Huawei Cloud DCS (Redis)
Collect Huawei Cloud DCS Metrics data
Configuration¶
Install Func¶
It is recommended to activate Guance Integration - Extensions - DataFlux Func (Automata): all prerequisites are automatically installed, please proceed with the script installation.
If you deploy Func manually, refer to Manual Func Deployment
Install Script¶
Note: Please prepare the Huawei Cloud AK that meets the requirements in advance (for simplicity, you can directly grant the global read-only permission
Tenant Guest)
Automata Version Script Activation¶
- Log in to the Guance console.
- Click the [Integration] menu and select [Cloud Account Management].
- Click [Add Cloud Account], select [Huawei Cloud], and fill in the required information on the interface. If the cloud account information has been configured before, ignore this step.
- Click [Test], and after the test is successful, click [Save]. If the test fails, please check whether the relevant configuration information is correct and test again.
- Click [Cloud Account Management] to see the added cloud account in the list. Click the corresponding cloud account to enter the details page.
- Click the [Integration] button on the cloud account details page. In the
Not Installedlist, findHuawei Cloud DCSand click the [Install] button. A pop-up installation interface will appear for installation.
Manual Script Activation¶
-
Log in to the Func console, click [Script Market], enter the Guance script market, and search for
integration_huaweicloud_dcs: Huawei Cloud DCS Metrics Collection.integration_huaweicloud_dcs_slowlog: Huawei Cloud DCS Slow Log Collection. -
Click [Install], then enter the corresponding parameters: Huawei Cloud AK, SK, and account name.
-
Click [Deploy Startup Script], the system will automatically create the
Startupscript set and automatically configure the corresponding startup script. -
After enabling, you can see the corresponding automatic trigger configuration in "Management / Automatic Trigger Configuration". Click [Execute] to execute it immediately without waiting for the scheduled time. After a while, you can check the execution task records and corresponding logs.
Verification¶
- In "Management / Automatic Trigger Configuration", confirm whether the corresponding task has the corresponding automatic trigger configuration, and check the corresponding task records and logs to see if there are any exceptions.
- In Guance, check whether asset information exists in "Infrastructure - Resource Catalog".
- In Guance, check whether there is corresponding monitoring data in "Metrics".
- In Guance, check whether there is corresponding log data in "Logs".
Metrics¶
Configure Huawei Cloud DCS monitoring metrics. More metrics can be collected through configuration Huawei Cloud DCS Metrics Details
Redis 3.0 Instance Monitoring Metrics¶
Note:
- DCS Redis 3.0 has been discontinued and is no longer available for sale. It is recommended to use Redis 4.0 and above.
- For the dimensions of monitoring metrics, please refer to Dimensions.
| Metric ID | Metric Name | Metric Description | Value Range | Measurement Object | Monitoring Period (Original Metric) |
|---|---|---|---|---|---|
cpu_usage |
CPU Utilization | This metric samples the CPU usage of the measurement object multiple times within the statistical period, representing the highest value of multiple samples. Unit: %. For single-node/primary-standby instances, this metric is the CPU value of the primary node. For Proxy cluster instances, this metric is the average value of each Proxy node. | 0-100% | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
memory_usage |
Memory Utilization | This metric is used to count the memory utilization of the measurement object. Unit: %. Note: Memory utilization statistics deduct reserved memory. | 0-100% | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
net_in_throughput |
Network Input Throughput | This metric is used to count the average input traffic per second of the network port. Unit: byte/s. | >=0 bytes/second | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
net_out_throughput |
Network Output Throughput | This metric is used to count the average output traffic per second of the network port. Unit: byte/s. | >=0 bytes/second | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
connected_clients |
Active Client Count | This metric is used to count the number of connected clients, including system monitoring, configuration synchronization, and business-related connections, excluding connections from slave nodes. | >=0 | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
client_longest_out_list |
Client Longest Output List | This metric is used to count the longest output list of all existing client connections. | >=0 | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
client_biggest_in_buf |
Client Maximum Input Buffer | This metric is used to count the maximum input data length of all existing client connections. Unit: byte. | >=0 byte | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
blocked_clients |
Blocked Client Count | This metric is used to count the number of clients suspended by blocking operations. Blocking operations include BLPOP, BRPOP, BRPOPLPUSH. | >=0 | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
used_memory |
Used Memory | This metric is used to count the number of memory bytes used by Redis. Unit: byte. | >=0 byte | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
used_memory_rss |
Used Memory RSS | This metric is used to count the RSS memory used by Redis. That is, the actual memory "resident in memory", including heap memory but excluding swapped-out memory. Unit: byte. | >=0 byte | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
used_memory_peak |
Used Memory Peak | This metric is used to count the peak memory usage since the Redis server started. Unit: byte. | >=0 byte | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
used_memory_lua |
Lua Used Memory | This metric is used to count the number of memory bytes used by the Lua engine. Unit: byte. | >=0 byte | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
memory_frag_ratio |
Memory Fragmentation Rate | This metric is used to count the current memory fragmentation rate. Numerically, it equals used_memory_rss / used_memory. | >=0 | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
total_connections_received |
New Connection Count | This metric is used to count the number of new connections within the statistical period. | >=0 | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
total_commands_processed |
Processed Command Count | This metric is used to count the number of commands processed within the statistical period. | >=0 | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
instantaneous_ops |
Instantaneous Operations Per Second | This metric is used to count the number of commands processed per second. | >=0 | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
total_net_input_bytes |
Network Received Bytes | This metric is used to count the number of bytes received within the statistical period. Unit: byte. | >=0 byte | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
total_net_output_bytes |
Network Sent Bytes | This metric is used to count the number of bytes sent within the statistical period. Unit: byte. | >=0 byte | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
instantaneous_input_kbps |
Instantaneous Network Input Traffic | This metric is used to count the instantaneous input traffic. Unit: KB/s. | >=0 KB/s | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
instantaneous_output_kbps |
Instantaneous Network Output Traffic | This metric is used to count the instantaneous output traffic. Unit: KB/s. | >=0 KB/s | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
rejected_connections |
Rejected Connection Count | This metric is used to count the number of connections rejected due to exceeding maxclients within the statistical period. | >=0 | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
expired_keys |
Expired Key Count | This metric is used to count the number of keys deleted due to expiration within the statistical period | >=0 | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
evicted_keys |
Evicted Key Count | This metric is used to count the number of keys deleted due to insufficient memory within the statistical period. | >=0 | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
keyspace_hits |
Keyspace Hit Count | This metric is used to count the number of hits in the main dictionary within the statistical period. | >=0 | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
keyspace_misses |
Keyspace Miss Count | This metric is used to count the number of misses in the main dictionary within the statistical period. | >=0 | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
pubsub_channels |
Pubsub Channel Count | This metric is used to count the number of Pub/Sub channels. | >=0 | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
pubsub_patterns |
Pubsub Pattern Count | This metric is used to count the number of Pub/Sub patterns. | >=0 | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
keyspace_hits_perc |
Cache Hit Rate | This metric is used to count the cache hit rate of Redis, calculated as: keyspace_hits/(keyspace_hits+keyspace_misses) Unit: %. |
0-100% | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
command_max_delay |
Command Maximum Latency | This metric is used to count the maximum latency of instance commands. Unit: ms. | >=0 ms | Redis Instance (Single-node/Primary-standby/Cluster) | 1 minute |
auth_errors |
Authentication Failure Count | This metric is used to count the number of authentication failures. | >=0 | Redis Instance (Single-node/Primary-standby) | 1 minute |
is_slow_log_exist |
Slow Log Existence | This metric is used to count whether slow logs exist in the instance. Note: This monitoring does not count slow logs caused by migrate, slaveof, config, bgsave, bgrewriteaof commands. |
1: Indicates existence. 0: Indicates non-existence. | Redis Instance (Single-node/Primary-standby) | 1 minute |
keys |
Total Cache Keys | This metric is used to count the total number of keys in the Redis cache. | >=0 | Redis Instance (Single-node/Primary-standby) | 1 minute |
Redis 4.0, Redis 5.0, and Redis 6.0 Instance Monitoring Metrics¶
Note:
- For the dimensions of monitoring metrics, please refer to Dimensions.
- Instance monitoring is the monitoring of data aggregated from the primary node.
- Some instance monitoring metrics are aggregated from both primary and slave nodes. Please refer to the description in "Metric Description" in Table 3.
| Metric ID | Metric Name | Metric Description | Value Range | Measurement Object | Monitoring Period (Original Metric) |
|---|---|---|---|---|---|
cpu_usage |
CPU Utilization | This metric samples the CPU usage of the measurement object multiple times within the statistical period, representing the highest value of multiple samples. Unit: %. | 0-100% | Redis Instance (Single-node/Primary-standby/Read-write Separation) | 1 minute |
cpu_avg_usage |
CPU Average Utilization | This metric samples the CPU usage of the measurement object multiple times within the statistical period, representing the average value of multiple samples. Unit: %. | 0-100% | Redis Instance (Single-node/Primary-standby/Read-write Separation) | 1 minute |
command_max_delay |
Command Maximum Latency | This metric is used to count the maximum latency of instance commands. Unit: ms. | >=0 ms | Redis Instance | 1 minute |
total_connections_received |
New Connection Count | This metric is used to count the number of new connections within the statistical period. | >=0 | Redis Instance | 1 minute |
is_slow_log_exist |
Slow Log Existence | This metric is used to count whether slow logs exist in the instance.Note: This monitoring does not count slow logs caused by migrate, slaveof, config, bgsave, bgrewriteaof commands. |
1: Indicates existence. 0: Indicates non-existence. | Redis Instance | 1 minute |
memory_usage |
Memory Utilization | This metric is used to count the memory utilization of the measurement object. Unit: %. | 0-100% | Redis Instance | 1 minute |
expires |
Total Expiring Keys | This metric is used to count the number of keys in the Redis cache that will expire. | >=0 | Redis Instance | 1 minute |
keyspace_hits_perc |
Cache Hit Rate | This metric is used to count the cache hit rate of Redis, calculated as: _hits/(keyspace_hits+keyspace_misses) Aggregated from both primary and slave nodes. Unit: %. |
0-100% | Redis Instance | 1 minute |
used_memory |
Used Memory | This metric is used to count the number of memory bytes used by Redis. Unit: Can be selected in the console, such as KB, MB, byte, etc. | >=0 | Redis Instance | 1 minute |
used_memory_dataset |
Dataset Used Memory | This metric is used to count the memory used by the dataset in Redis. Unit: Can be selected in the console, such as KB, MB, byte, etc. | >=0 | Redis Instance | 1 minute |
used_memory_dataset_perc |
Dataset Used Memory Percentage | This metric is used to count the percentage of memory used by the dataset in Redis. Aggregated from both primary and slave nodes. Unit: %. | 0-100% | Redis Instance | 1 minute |
used_memory_rss |
Used Memory RSS | This metric is used to count the RSS memory used by Redis. That is, the actual memory "resident in memory", including heap memory but excluding swapped-out memory. Unit: Can be selected in the console, such as KB, MB, byte, etc. | >=0 | Redis Instance | 1 minute |
instantaneous_ops |
Instantaneous Operations Per Second | This metric is used to count the number of commands processed per second. | >=0 | Redis Instance | 1 minute |
keyspace_misses |
Keyspace Miss Count | This metric is used to count the number of misses in the main dictionary within the statistical period. Aggregated from both primary and slave nodes. | >=0 | Redis Instance | 1 minute |
keys |
Total Cache Keys | This metric is used to count the total number of keys in the Redis cache. | >=0 | Redis Instance | 1 minute |
blocked_clients |
Blocked Client Count | This metric is used to count the number of clients suspended by blocking operations. | >=0 | Redis Instance | 1 minute |
connected_clients |
Active Client Count | This metric is used to count the number of connected clients, including system monitoring, configuration synchronization, and business-related connections, excluding connections from slave nodes. | >=0 | Redis Instance | 1 minute |
del |
DEL | This metric is used to count the average number of del operations per second. Unit: Count/s | 0-500000 Count/s | Redis Instance | 1 minute |
evicted_keys |
Evicted Key Count | This metric is used to count the number of keys deleted due to insufficient memory within the statistical period. Aggregated from both primary and slave nodes. | >=0 | Redis Instance | 1 minute |
expire |
EXPIRE | This metric is used to count the average number of expire operations per second. Unit: Count/s | 0-500000 Count/s | Redis Instance | 1 minute |
expired_keys |
Expired Key Count | This metric is used to count the number of keys deleted due to expiration within the statistical period. Aggregated from both primary and slave nodes. | >=0 | Redis Instance | 1 minute |
get |
GET | This metric is used to count the average number of get operations per second. Aggregated from both primary and slave nodes. Unit: Count/s | 0-500000 Count/s | Redis Instance | 1 minute |
hdel |
HDEL | This metric is used to count the average number of hdel operations per second. Unit: Count/s | 0-500000 Count/s | Redis Instance | 1 minute |
hget |
HGET | This metric is used to count the average number of hget operations per second. Aggregated from both primary and slave nodes. Unit: Count/s | 0-500000 Count/s | Redis Instance | 1 minute |
hmget |
HMGET | This metric is used to count the average number of hmget operations per second. Aggregated from both primary and slave nodes. Unit: Count/s | 0-500000 Count/s | Redis Instance | 1 minute |
hmset |
HMSET | This metric is used to count the average number of hmset operations per second. Unit: Count/s | 0-500000 Count/s | Redis Instance | 1 minute |
hset |
HSET | This metric is used to count the average number of hset operations per second. Unit: Count/s | 0-500000 Count/s | Redis Instance | 1 minute |
instantaneous_input_kbps |
Instantaneous Network Input Traffic | This metric is used to count the instantaneous input traffic. Unit: KB/s. | >=0 KB/s | Redis Instance | 1 minute |
instantaneous_output_kbps |
Instantaneous Network Output Traffic | This metric is used to count the instantaneous output traffic. Unit: KB/s. | >=0 KB/s | Redis Instance | 1 minute |
memory_frag_ratio |
Memory Fragmentation Rate | This metric is used to count the current memory fragmentation rate | >=0 | Redis Instance | 1 minute |
mget |
MGET | This metric is used to count the average number of mget operations per second. Aggregated from both primary and slave nodes. Unit: Count/s | 0-500000 Count/s | Redis Instance | 1 minute |
mset |
MSET | This metric is used to count the average number of mset operations per second. Unit: Count/s | 0-500000 Count/s | Redis Instance | 1 minute |
pubsub_channels |
Pubsub Channel Count | This metric is used to count the number of Pub/Sub channels. | >=0 | Redis Instance | 1 minute |
pubsub_patterns |
Pubsub Pattern Count | This metric is used to count the number of Pub/Sub patterns. | >=0 | Redis Instance | 1 minute |
set |
SET | This metric is used to count the average number of set operations per second. Unit: Count/s | 0-500000 Count/s | Redis Instance | 1 minute |
used_memory_lua |
Lua Used Memory | This metric is used to count the number of memory bytes used by the Lua engine. Unit: Can be selected in the console, such as KB, MB, byte, etc. | >=0 | Redis Instance | 1 minute |
used_memory_peak |
Used Memory Peak | This metric is used to count the peak memory usage since the Redis server started. Unit: Can be selected in the console, such as KB, MB, byte, etc. | >=0 | Redis Instance | 1 minute |
sadd |
Sadd | This metric is used to count the average number of sadd operations per second. Unit: Count/s | 0-500000 Count/s | Redis Instance | 1 minute |
smembers |
Smembers | This metric is used to count the average number of smembers operations per second. Aggregated from both primary and slave nodes. Unit: Count/s | 0-500000 Count/s | Redis Instance | 1 minute |
setex |
SETEX | This metric is used to count the number of setex operations per second. Unit: Count/s | 0-500000 Count/s | Redis Instance | 1 minute |
rx_controlled |
Flow Control Count | This metric is used to count the number of times flow control was triggered within the statistical period. A value greater than 0 indicates that the current bandwidth usage exceeds the maximum bandwidth limit and flow control is triggered. Unit: Count. | >=0 | Redis Instance | 1 minute |
bandwidth_usage |
Bandwidth Utilization | This metric is used to calculate the percentage of current traffic bandwidth to the maximum bandwidth limit. | 0-200% | Redis Instance | 1 minute |
command_max_rt |
Maximum Latency | This metric is used to count the maximum latency from receiving a command to sending a response. Unit: us. | >=0 us | Redis Instance (Single-node) | 1 minute |
command_avg_rt |
Average Latency | This metric is used to count the average latency from receiving a command to sending a response. Unit: us. | >=0 us | Redis Instance (Single-node) | 1 minute |
Redis Instance Data Node Monitoring Metrics¶
Note:
- Redis primary-standby, read-write separation, and cluster instances support data node monitoring.
- For the dimensions of monitoring metrics, please refer to Dimensions.
| Metric ID | Metric Name | Metric Description | Value Range | Measurement Object | Monitoring Period (Original Metric) |
|---|---|---|---|---|---|
cpu_usage |
CPU Utilization | This metric samples the CPU usage of the measurement object multiple times within the statistical period, representing the highest value of multiple samples. Unit: %. | 0-100% | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
cpu_avg_usage |
CPU Average Utilization | This metric samples the CPU usage of the measurement object multiple times within the statistical period, representing the average value of multiple samples. Unit: %. | 0-100% | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
memory_usage |
Memory Utilization | This metric is used to count the memory utilization of the measurement object. Unit: %. | 0-100% | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
connected_clients |
Active Client Count | This metric is used to count the number of connected clients, including system monitoring, configuration synchronization, and business-related connections, excluding connections from slave nodes. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
client_longest_out_list |
Client Longest Output List | This metric is used to count the longest output list of all existing client connections. | >=0 | Redis 3.0, 4.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
client_biggest_in_buf |
Client Maximum Input Buffer | This metric is used to count the maximum input data length of all existing client connections. Unit: Can be selected in the console, such as KB, MB, byte, etc. | >=0 | Redis 3.0, 4.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
blocked_clients |
Blocked Client Count | This metric is used to count the number of clients suspended by blocking operations. Blocking operations include BLPOP, BRPOP, BRPOPLPUSH. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
used_memory |
Used Memory | This metric is used to count the number of memory bytes used by Redis. Unit: Can be selected in the console, such as KB, MB, byte, etc. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
used_memory_rss |
Used Memory RSS | This metric is used to count the RSS memory used by Redis. That is, the actual memory "resident in memory", including heap memory but excluding swapped-out memory. Unit: Can be selected in the console, such as KB, MB, byte, etc. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
used_memory_peak |
Used Memory Peak | This metric is used to count the peak memory usage since the Redis server started. Unit: Can be selected in the console, such as KB, MB, byte, etc. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
used_memory_lua |
Lua Used Memory | This metric is used to count the number of memory bytes used by the Lua engine. Unit: Can be selected in the console, such as KB, MB, byte, etc. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
memory_frag_ratio |
Memory Fragmentation Rate | This metric is used to count the current memory fragmentation rate. Numerically, it equals used_memory_rss / used_memory. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
total_connections_received |
New Connection Count | This metric is used to count the number of new connections within the statistical period. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
total_commands_processed |
Processed Command Count | This metric is used to count the number of commands processed within the statistical period. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
instantaneous_ops |
Instantaneous Operations Per Second | This metric is used to count the number of commands processed per second. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
total_net_input_bytes |
Network Received Bytes | This metric is used to count the number of bytes received within the statistical period. Unit: Can be selected in the console, such as KB, MB, byte, etc. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
total_net_output_bytes |
Network Sent Bytes | This metric is used to count the number of bytes sent within the statistical period. Unit: Can be selected in the console, such as KB, MB, byte, etc. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
instantaneous_input_kbps |
Instantaneous Network Input Traffic | This metric is used to count the instantaneous input traffic. Unit: KB/s. | >=0 KB/s | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
instantaneous_output_kbps |
Instantaneous Network Output Traffic | This metric is used to count the instantaneous output traffic. Unit: KB/s. | >=0 KB/s | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
| rejected_connections | Rejected Connection Count | This metric is used to count the number of connections rejected due to exceeding maxclients within the statistical period. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
expired_keys |
Expired Key Count | This metric is used to count the number of keys deleted due to expiration within the statistical period. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
evicted_keys |
Evicted Key Count | This metric is used to count the number of keys deleted due to insufficient memory within the statistical period. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
pubsub_channels |
Pubsub Channel Count | This metric is used to count the number of Pub/Sub channels. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
pubsub_patterns |
Pubsub Pattern Count | This metric is used to count the number of Pub/Sub patterns. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
keyspace_hits_perc |
Cache Hit Rate | This metric is used to count the cache hit rate of Redis, calculated as: keyspace_hits/(keyspace_hits+keyspace_misses) Unit: %. | 0-100% | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
command_max_delay |
Command Maximum Latency | This metric is used to count the maximum latency of node commands. Unit: ms. | >=0 ms | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
is_slow_log_exist |
Slow Log Existence | This metric is used to count whether slow logs exist in the node.Note: This monitoring does not count slow queries caused by migrate, slaveof, config, bgsave, bgrewriteaof commands. |
1: Indicates existence. 0: Indicates non-existence. | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
keys |
Total Cache Keys | This metric is used to count the total number of keys in the Redis cache. | >=0 | Redis Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
sadd |
SADD | This metric is used to count the average number of sadd operations per second. Unit: Count/s | 0-500000 Count/s | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
smembers |
SMEMBERS | This metric is used to count the average number of smembers operations per second. Unit: Count/s | 0-500000 Count/s | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
ms_repl_offset |
Primary-Slave Data Synchronization Difference | This metric is used to count the data synchronization difference between primary and slave nodes. | - | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes Slave Node | 1 minute |
del |
DEL | This metric is used to count the average number of del operations per second. Unit: Count/s | 0-500000 Count/s | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
expire |
EXPIRE | This metric is used to count the average number of expire operations per second. Unit: Count/s | 0-500000 Count/s | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
get |
GET | This metric is used to count the average number of get operations per second. Unit: Count/s | 0-500000 Count/s | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
hdel |
HDEL | This metric is used to count the average number of hdel operations per second. Unit: Count/s | 0-500000 Count/s | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
hget |
HGET | This metric is used to count the average number of hget operations per second. Unit: Count/s | 0-500000 Count/s | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
hmget |
HMGET | This metric is used to count the average number of hmget operations per second. Unit: Count/s | 0-500000 Count/s | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
hmset |
HMSET | This metric is used to count the average number of hmset operations per second. Unit: Count/s | 0-500000 Count/s | Redis 4.0/Redis 5.0 Primary-standby, Cluster, Redis 6.0 Primary-standby Instance Data Nodes | 1 minute |
hset |
HSET | This metric is used to count the average number of hset operations per second. Unit: Count/s | 0-500000 Count/s | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
mget |
MGET | This metric is used to count the average number of mget operations per second. Unit: Count/s | 0-500000 Count/s | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
mset |
MSET | This metric is used to count the average number of mset operations per second. Unit: Count/s | 0-500000 Count/s | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
set |
SET | This metric is used to count the average number of set operations per second. Unit: Count/s | 0-500000 Count/s | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
rx_controlled |
Flow Control Count | This metric is used to count the number of times flow control was triggered within the statistical period. A value greater than 0 indicates that the current bandwidth usage exceeds the maximum bandwidth limit and flow control is triggered. Unit: Count. | >=0 | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
bandwidth_usage |
Bandwidth Utilization | This metric is used to calculate the percentage of current traffic bandwidth to the maximum bandwidth limit. | 0-200% | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
connections_usage |
Connection Utilization | This metric is used to count the percentage of current connections to the maximum connection limit. Unit: %. | 0-100% | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
command_max_rt |
Maximum Latency | This metric is used to count the maximum latency from receiving a command to sending a response. Unit: us. | >=0 us | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
command_avg_rt |
Average Latency | This metric is used to count the average latency from receiving a command to sending a response. Unit: us. | >=0 us | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
sync_full |
Full Synchronization Count | This metric is used to count the total number of full synchronizations completed since the Redis server started. | >=0 | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
slow_log_counts |
Slow Log Occurrence Count | This metric is used to count the number of times slow logs appeared within a statistical period. | >=0 | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
setex |
SETEX | This metric is used to count the number of setex operations per second. Unit: Count/s | 0-500000 Count/s | Redis 4.0, 5.0, 6.0 Version Primary-standby, Read-write Separation, Cluster Instance Data Nodes | 1 minute |
Proxy Node Monitoring Metrics¶
Note:
- Proxy cluster and read-write separation instances support Proxy node monitoring metrics.
- For the dimensions of monitoring metrics, please refer to Dimensions.
| Metric ID | Metric Name | Metric Description | Value Range | Measurement Object | Monitoring Period (Original Metric) |
|---|---|---|---|---|---|
| cpu_usage | CPU Utilization | This metric samples the CPU usage of the measurement object multiple times within the statistical period, representing the highest value of multiple samples. Unit: %. | 0-100% | Redis 3.0 Proxy Cluster Instance Proxy Node | 1 minute |
| memory_usage | Memory Utilization | This metric is used to count the memory utilization of the measurement object. Unit: %. | 0-100% | Redis 3.0 Proxy Cluster Instance Proxy Node | 1 minute |
| p_connected_clients | Active Client Count | This metric is used to count the number of connected clients. | >=0 | Redis 3.0 Proxy Cluster Instance Proxy Node | 1 minute |
| max_rxpck_per_sec | Network Packet Receive Maximum Rate | This metric is used to count the maximum number of data packets received per second by the network card of the measurement object within the statistical period. Unit: packets/second | 0-10000000 packets/second | Redis 3.0 Proxy Cluster Instance Proxy Node | 1 minute |
| max_txpck_per_sec | Network Packet Send Maximum Rate | This metric is used to count the maximum number of data packets sent per second by the network card of the measurement object within the statistical period. Unit: packets/second | 0-10000000 packets/second | Redis 3.0 Proxy Cluster Instance Proxy Node | 1 minute |
| max_rxkB_per_sec | Network Input Maximum Bandwidth | This metric is used to count the maximum amount of data received per second by the network card of the measurement object. Unit: KB/s. | >= 0KB/s | Redis 3.0 Proxy Cluster Instance Proxy Node | 1 minute |
| max_txkB_per_sec | Network Output Maximum Bandwidth | This metric is used to count the maximum amount of data sent per second by the network card of the measurement object. Unit: KB/s. | >= 0KB/s | Redis 3.0 Proxy Cluster Instance Proxy Node | 1 minute |
| avg_rxpck_per_sec | Network Packet Receive Average Rate | This metric is used to count the average number of data packets received per second by the network card of the measurement object within the statistical period. Unit: packets/second | 0-10000000 packets/second | Redis 3.0 Proxy Cluster Instance Proxy Node | 1 minute |
| avg_txpck_per_sec | Network Packet Send Average Rate | This metric is used to count the average number of data packets sent per second by the network card of the measurement object within the statistical period. Unit: packets/second | 0-10000000 packets/second | Redis 3.0 Proxy Cluster Instance Proxy Node | 1 minute |
| avg_rxkB_per_sec | Network Input Average Bandwidth | This metric is used to count the average amount of data received per second by the network card of the measurement object. Unit: KB/s. | >= 0KB/s | Redis 3.0 Proxy Cluster Instance Proxy Node | 1 minute |
| avg_txkB_per_sec | Network Output Average Bandwidth | This metric is used to count the average amount of data sent per second by the network card of the measurement object. Unit: KB/s. | >= 0KB/s | Redis 3.0 Proxy Cluster Instance Proxy Node | 1 minute |
| Metric ID | Metric Name | Metric Description | Value Range | Measurement Object | Monitoring Period (Original Metric) |
|---|---|---|---|---|---|
node_status |
Instance Node Status | This metric is used to display whether the Proxy node status is normal. | 0: Indicates normal. 1: Indicates abnormal. | Proxy Cluster, Read-write Separation Instance Proxy Node | 1 minute |
cpu_usage |
CPU Utilization | This metric samples the CPU usage of the measurement object multiple times within the statistical period, representing the highest value of multiple samples. Unit: %. | 0-100% | Proxy Cluster, Read-write Separation Instance Proxy Node | 1 minute |
cpu_avg_usage |
CPU Average Utilization | This metric samples the CPU usage of the measurement object multiple times within the statistical period, representing the average value of multiple samples. Unit: %. | 0-100% | Proxy Cluster, Read-write Separation Instance Proxy Node | 1 minute |
memory_usage |
Memory Utilization | This metric is used to count the memory utilization of the measurement object. Unit: %. | 0-100% | Proxy Cluster, Read-write Separation Instance Proxy Node | 1 minute |
connected_clients |
Active Client Count | This metric is used to count the number of connected clients, including system monitoring, configuration synchronization, and business-related connections, excluding connections from slave nodes. | >=0 | Proxy Cluster, Read-write Separation Instance Proxy Node | 1 minute |
instantaneous_ops |
Instantaneous Operations Per Second | This metric is used to count the number of commands processed per second. | >=0 | Proxy Cluster, Read-write Separation Instance Proxy Node | 1 minute |
instantaneous_input_kbps |
Instantaneous Network Input Traffic | This metric is used to count the instantaneous input traffic. Unit: KB/s. | >=0KB/s | Proxy Cluster, Read-write Separation Instance Proxy Node | 1 minute |
instantaneous_output_kbps |
Instantaneous Network Output Traffic | This metric is used to count the instantaneous output traffic. Unit: KB/s. | >=0KB/s | Proxy Cluster, Read-write Separation Instance Proxy Node | 1 minute |
total_net_input_bytes |
Network Received Bytes | This metric is used to count the number of bytes received within the statistical period. Unit: Can be selected in the console, such as KB, MB, byte, etc. | >=0 | Proxy Cluster, Read-write Separation Instance Proxy Node | 1 minute |
total_net_output_bytes |
Network Sent Bytes | This metric is used to count the number of bytes sent within the statistical period. Unit: Can be selected in the console, such as KB, MB, byte, etc. | >=0 | Proxy Cluster, Read-write Separation Instance Proxy Node | 1 minute |
connections_usage |
Connection Utilization | This metric is used to count the percentage of current connections to the maximum connection limit. Unit: %. | 0-100% | Proxy Cluster, Read-write Separation Instance Proxy Node | 1 minute |
command_max_rt |
Maximum Latency | This metric is used to count the maximum latency from receiving a command to sending a response. Unit: us. | >=0us | Proxy Cluster, Read-write Separation Instance Proxy Node | 1 minute |
command_avg_rt |
Average Latency | This metric is used to count the average latency from receiving a command to sending a response. Unit: us. | >=0us | Proxy Cluster, Read-write Separation Instance Proxy Node | 1 minute |
Memcached Instance Monitoring Metrics¶
Note:
For the dimensions of monitoring metrics, please refer to Dimensions.
| Metric ID | Metric Name | Metric Description | Value Range | Measurement Object | Monitoring Period (Original Metric) |
|---|---|---|---|---|---|
cpu_usage |
CPU Utilization | This metric samples the CPU usage of the measurement object multiple times within the statistical period, representing the highest value of multiple samples. Unit: %. | 0-100% | Memcached Instance | 1 minute |
memory_usage |
Memory Utilization | This metric is used to count the memory utilization of the measurement object. Unit: %. | 0-100% | Memcached Instance | 1 minute |
net_in_throughput |
Network Input Throughput | This metric is used to count the average input traffic per second of the network port. Unit: byte/s. | >= 0byte/s | Memcached Instance | 1 minute |
net_out_throughput |
Network Output Throughput | This metric is used to count the average output traffic per second of the network port. Unit: byte/s. | >= 0byte/s | Memcached Instance | 1 minute |
mc_connected_clients |
Active Client Count | This metric is used to count the number of connected clients, excluding connections from slave nodes. | >=0 | Memcached Instance | 1 minute |
mc_used_memory |
Used Memory | This metric is used to count the number of memory bytes used. Unit: byte. | >=0byte | Memcached Instance | 1 minute |
mc_used_memory_rss |
Used Memory RSS | This metric is used to count the RSS memory used. That is, the actual memory "resident in memory", including heap memory but excluding swapped-out memory. Unit: byte. | >=0byte | Memcached Instance | 1 minute |
mc_used_memory_peak |
Used Memory Peak | This metric is used to count the peak memory usage since the server started. Unit: byte. | >=0byte | Memcached Instance | 1 minute |
mc_memory_frag_ratio |
Memory Fragmentation Rate | This metric is used to count the current memory fragmentation rate. Numerically, it equals used_memory_rss / used_memory. | >=0 | Memcached Instance | 1 minute |
mc_connections_received |
New Connection Count | This metric is used to count the number of new connections within the statistical period. | >=0 | Memcached Instance | 1 minute |
mc_commands_processed |
Processed Command Count | This metric is used to count the number of commands processed within the statistical period. | >=0 | Memcached Instance | 1 minute |
mc_instantaneous_ops |
Instantaneous Operations Per Second | This metric is used to count the number of commands processed per second. | >=0 | Memcached Instance | 1 minute |
mc_net_input_bytes |
Network Received Bytes | This metric is used to count the number of bytes received within the statistical period. Unit: byte. | >=0byte | Memcached Instance | 1 minute |
mc_net_output_bytes |
Network Sent Bytes | This metric is used to count the number of bytes sent within the statistical period. Unit: byte. | >=0byte | Memcached Instance | 1 minute |
mc_instantaneous_input_kbps |
Instantaneous Network Input Traffic | This metric is used to count the instantaneous input traffic. Unit: KB/s. | >=0KB/s | Memcached Instance | 1 minute |
mc_instantaneous_output_kbps |
Instantaneous Network Output Traffic | This metric is used to count the instantaneous output traffic. Unit: KB/s. | >=0KB/s | Memcached Instance | 1 minute |
mc_rejected_connections |
Rejected Connection Count | This metric is used to count the number of connections rejected due to exceeding maxclients within the statistical period. | >=0 | Memcached Instance | 1 minute |
mc_expired_keys |
Expired Key Count | This metric is used to count the number of keys deleted due to expiration within the statistical period. | >=0 | Memcached Instance | 1 minute |
mc_evicted_keys |
Evicted Key Count | This metric is used to count the number of keys deleted due to insufficient memory within the statistical period. | >=0 | Memcached Instance | 1 minute |
mc_cmd_get |
Data Query Request Count | This metric is used to count the number of data query requests received by the service. | >=0 | Memcached Instance | 1 minute |
mc_cmd_set |
Data Storage Request Count | This metric is used to count the number of data storage requests received by the service. | >=0 | Memcached Instance | 1 minute |
mc_cmd_flush |
Data Clear Request Count | This metric is used to count the number of data clear requests received by the service. | >=0 | Memcached Instance | 1 minute |
mc_cmd_touch |
Data Expiration Modification Request Count | This metric is used to count the number of data expiration modification requests received by the service. | >=0 | Memcached Instance | 1 minute |
mc_get_hits |
Data Query Hit Count | This metric is used to count the number of successful data queries. | >=0 | Memcached Instance | 1 minute |
mc_get_misses |
Data Query Miss Count | This metric is used to count the number of failed data queries due to non-existent keys. | >=0 | Memcached Instance | 1 minute |
mc_delete_hits |
Data Delete Hit Count | This metric is used to count the number of successful data deletions. | >=0 | Memcached Instance | 1 minute |
mc_delete_misses |
Data Delete Miss Count | This metric is used to count the number of failed data deletions due to non-existent keys. | >=0 | Memcached Instance | 1 minute |
mc_incr_hits |
Arithmetic Increment Hit Count | This metric is used to count the number of successful arithmetic increment operations. | >=0 | Memcached Instance | 1 minute |
mc_incr_misses |
Arithmetic Increment Miss Count | This metric is used to count the number of failed arithmetic increment operations due to non-existent keys. | >=0 | Memcached Instance | 1 minute |
mc_decr_hits |
Arithmetic Decrement Hit Count | This metric is used to count the number of successful arithmetic decrement operations. | >=0 | Memcached Instance | 1 minute |
mc_decr_misses |
Arithmetic Decrement Miss Count | This metric is used to count the number of failed arithmetic decrement operations due to non-existent keys. | >=0 | Memcached Instance | 1 minute |
mc_cas_hits |
CAS Hit Count | This metric is used to count the number of successful CAS operations. | >=0 | Memcached Instance | 1 minute |
mc_cas_misses |
CAS Miss Count | This metric is used to count the number of failed CAS operations due to non-existent keys. | >=0 | Memcached Instance | 1 minute |
mc_cas_badval |
CAS Value Mismatch Count | This metric is used to count the number of failed CAS operations due to value mismatch. | >=0 | Memcached Instance | 1 minute |
mc_touch_hits |
Data Expiration Modification Hit Count | This metric is used to count the number of successful data expiration modifications. | >=0 | Memcached Instance | 1 minute |
mc_touch_misses |
Data Expiration Modification Miss Count | This metric is used to count the number of failed data expiration modifications due to non-existent keys. | >=0 | Memcached Instance | 1 minute |
mc_auth_cmds |
Authentication Request Count | This metric is used to count the number of authentication requests. | >=0 | Memcached Instance | 1 minute |
mc_auth_errors |
Authentication Failure Count | This metric is used to count the number of authentication failures. | >=0 | Memcached Instance | 1 minute |
mc_curr_items |
Stored Data Entries | This metric is used to count the number of stored data entries. | >=0 | Memcached Instance | 1 minute |
mc_command_max_delay |
Command Maximum Latency | This metric is used to count the maximum latency of commands. Unit: ms. | >=0ms | Memcached Instance | 1 minute |
mc_is_slow_log_exist |
Slow Log Existence | This metric is used to count whether slow logs exist in the instance.Note: This monitoring does not count slow logs caused by migrate, slaveof, config, bgsave, bgrewriteaof commands. |
1: Indicates existence. 0: Indicates non-existence. | Memcached Instance | 1 minute |
mc_keyspace_hits_perc |
Access Hit Rate | This metric is used to count the access code hit rate of the instance. Unit: %. | 0-100% | Memcached Instance | 1 minute |
Object¶
The collected Huawei Cloud DCS object data structure can be seen in "Infrastructure - Resource Catalog".
{
"measurement": "huaweicloud_redis",
"tags": {
"RegionId" : "cn-north-4",
"project_id" : "c631f04625xxxxxxxxxxf253c62d48585",
"enterprise_project_id" : "71be0037-xxxx-xxxx-xxxx-b6b91f134066",
"instance_id" : "71be0037-xxxx-xxxx-xxxx-b6b91f134066",
"instance_name" : "dcs-iash",
"engine" : "Redis",
},
"fields": {
"engine_version" : "5.0",
"status" : "RUNNING",
"port" : "6379",
"ip" : "192.xxx.x.144",
"charging_mode" : "0",
"enable_publicip" : "False",
"spec_code" : "xxxx",
"az_codes" : "xxxxx",
"created_at" : "2022-07-12T07:29:56.875Z",
"max_memory" : "128",
"used_memory" : "2",
"capacity" : "0",
"description" : "",
}
}
Partial field descriptions are as follows:
| Field | Type | Description |
|---|---|---|
ip |
String | The IP address to connect to the cache instance. If it is a cluster instance, multiple IP addresses are returned, separated by commas. For example: 192.168.0.1, 192.168.0.2. |
charging_mode |
String | Billing mode, 0 indicates pay-as-you-go, 1 indicates subscription. |
no_password_access |
String | Whether to allow password-free access to the cache instance: true: The instance can be accessed without a password. false: The instance must be authenticated with a password to access. |
enable_publicip |
String | Whether the Redis cache instance has public network access enabled. True: Enabled. False: Not enabled. |
max_memory |
Integer | Total memory, unit: MB. |
used_memory |
Integer | Used memory, unit: MB. |
capacity |
Integer | Cache capacity (G Byte). |
status |
String | CREATING : The state after applying for a cache instance and before the cache instance state enters the running state. CREATEFAILED: The cache instance is in the creation failed state. RUNNING: The cache instance is in the normal running state. RESTARTING: The cache instance is performing a restart operation. FROZEN: The cache instance is in the frozen state, and users can renew the frozen cache instance in "My Orders". EXTENDING: The cache instance is in the expanding state. RESTORING: The cache instance is in the data recovery state. FLUSHING: The cache instance is in the data clearing state. |
Note: The fields in
tagsandfieldsmay change with subsequent updates.Tip 1: The value of
tags.instance_idis the instance ID, which is used as a unique identifier.Tip 2: The following fields are JSON serialized strings -
fields.message-tags.az_codes