Huawei Cloud DCS
Collect Huawei Cloud DCS Metrics
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.
If deploying Func manually, refer to Manual Deployment of Func
Install Script¶
Note: Please prepare the Huawei Cloud AK in advance (for simplicity, you can directly grant the global read-only permission
ReadOnlyAccess)
To synchronize Huawei Cloud DCS monitoring data, we install the corresponding collection scripts:
- integration_huaweicloud_dcs: Collect Huawei Cloud DCS Metrics
- integration_huaweicloud_dcs_slowlog: Collect Huawei Cloud DCS Slow Log Data
After clicking [Install], enter the corresponding parameters: Huawei Cloud AK, Huawei Cloud account name.
Click [Deploy Startup Script], the system will automatically create the Startup script set and automatically configure the corresponding startup script.
After the script is installed, find the script in Func under "Development" - "TrueWatch Integration (Huawei Cloud-DCS Collection)" / "TrueWatch Integration (Huawei Cloud-DCS Slow Query Log Collection)", expand and modify the script, find collector_configs and monitor_configs to edit the content in region_projects, change the region and Project ID to the actual region and Project ID, then click Save and Publish.
In addition, you can see the corresponding automatic trigger configuration under "Management / 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¶
- Under "Management / Automatic Trigger Configuration", confirm whether the corresponding task has the corresponding automatic trigger configuration, and you can also view the corresponding task records and logs to check for any abnormalities
- In TrueWatch, under "Infrastructure - Resource Catalog", check if asset information exists
- In TrueWatch, under "Metrics", check if there is corresponding monitoring data
- In TrueWatch, under "Logs", check if there is corresponding log data
Metrics¶
Configure Huawei Cloud DCS monitoring metrics, you can collect more metrics through configuration Huawei Cloud DCS Metric 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 or later versions.
- For the dimensions of monitoring metrics, please refer to Dimensions.
| Metric ID | Metric Name | Metric Description | Value Range | Measurement Object | Monitoring Cycle (Raw 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/standby instances, this metric is the CPU value of the master node. For Proxy cluster instances, this metric is the average value of each Proxy node. | 0-100% | Redis Instance (Single/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 are after deducting reserved memory. | 0-100% | Redis Instance (Single/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/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/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/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 connections of the client. | >=0 | Redis Instance (Single/Standby/Cluster) | 1 minute |
client_biggest_in_buf |
Client Largest Input Buffer | This metric is used to count the maximum input data length of all existing connections of the client. Unit: byte. | >=0 byte | Redis Instance (Single/Standby/Cluster) | 1 minute |
blocked_clients |
Blocked Client Count | This metric is used to count the number of clients suspended by blocking operations such as BLPOP, BRPOP, BRPOPLPUSH. | >=0 | Redis Instance (Single/Standby/Cluster) | 1 minute |
used_memory |
Used Memory | This metric is used to count the number of bytes of memory used by Redis. Unit: byte. | >=0 byte | Redis Instance (Single/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 memory actually resident "in memory". It includes heap memory but excludes swapped-out memory. Unit: byte. | >=0 byte | Redis Instance (Single/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/Standby/Cluster) | 1 minute |
used_memory_lua |
Lua Used Memory | This metric is used to count the number of bytes of memory used by the Lua engine. Unit: byte. | >=0 byte | Redis Instance (Single/Standby/Cluster) | 1 minute |
memory_frag_ratio |
Memory Fragmentation Ratio | This metric is used to count the current memory fragmentation ratio. Its value is equal to used_memory_rss / used_memory. | >=0 | Redis Instance (Single/Standby/Cluster) | 1 minute |
total_connections_received |
New Connections Count | This metric is used to count the number of new connections within the statistical period. | >=0 | Redis Instance (Single/Standby/Cluster) | 1 minute |
total_commands_processed |
Processed Commands Count | This metric is used to count the number of commands processed within the statistical period. | >=0 | Redis Instance (Single/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/Standby/Cluster) | 1 minute |
total_net_input_bytes |
Network Received Bytes Count | This metric is used to count the number of bytes received within the statistical period. Unit: byte. | >=0 byte | Redis Instance (Single/Standby/Cluster) | 1 minute |
total_net_output_bytes |
Network Sent Bytes Count | This metric is used to count the number of bytes sent within the statistical period. Unit: byte. | >=0 byte | Redis Instance (Single/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/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/Standby/Cluster) | 1 minute |
rejected_connections |
Rejected Connections Count | This metric is used to count the number of connections rejected due to exceeding maxclients within the statistical period. | >=0 | Redis Instance (Single/Standby/Cluster) | 1 minute |
expired_keys |
Expired Keys Count | This metric is used to count the number of keys deleted due to expiration within the statistical period | >=0 | Redis Instance (Single/Standby/Cluster) | 1 minute |
evicted_keys |
Evicted Keys Count | This metric is used to count the number of keys deleted due to insufficient memory within the statistical period. | >=0 | Redis Instance (Single/Standby/Cluster) | 1 minute |
keyspace_hits |
Keyspace Hits Count | This metric is used to count the number of hits in the main dictionary within the statistical period. | >=0 | Redis Instance (Single/Standby/Cluster) | 1 minute |
keyspace_misses |
Keyspace Misses Count | This metric is used to count the number of misses in the main dictionary within the statistical period. | >=0 | Redis Instance (Single/Standby/Cluster) | 1 minute |
pubsub_channels |
Pubsub Channels Count | This metric is used to count the number of Pub/Sub channels. | >=0 | Redis Instance (Single/Standby/Cluster) | 1 minute |
pubsub_patterns |
Pubsub Patterns Count | This metric is used to count the number of Pub/Sub patterns. | >=0 | Redis Instance (Single/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/Standby/Cluster) | 1 minute |
command_max_delay |
Command Maximum Delay | This metric is used to count the maximum delay of commands in the instance. Unit: ms. | >=0 ms | Redis Instance (Single/Standby) | 1 minute |
auth_errors |
Authentication Failures Count | This metric is used to count the number of authentication failures in the instance. | >=0 | Redis Instance (Single/Standby) | 1 minute |
is_slow_log_exist |
Whether Slow Log Exists | 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 existence0: Indicates non-existence. | Redis Instance (Single/Standby) | 1 minute |
keys |
Cache Key Total Count | This metric is used to count the total number of keys in the Redis cache. | >=0 | Redis Instance (Single/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 master node.
- Some instance monitoring metrics are aggregated from the master node 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 Cycle (Raw 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/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/Standby/Read-Write Separation) | 1 minute |
command_max_delay |
Command Maximum Delay | This metric is used to count the maximum delay of commands in the instance. Unit: ms. | >=0 ms | Redis Instance | 1 minute |
total_connections_received |
New Connections 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 |
Whether Slow Log Exists | 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 existence0: 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 |
Keys with Expiration Time Total Count | 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 the master node and slave nodes. Unit: %. |
0-100% | Redis Instance | 1 minute |
used_memory |
Used Memory | This metric is used to count the number of bytes of memory 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 relative to the total memory. Aggregated from the master node 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 memory actually resident "in memory". It includes heap memory but excludes 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 Misses Count | This metric is used to count the number of misses in the main dictionary within the statistical period. Aggregated from the master node and slave nodes. | >=0 | Redis Instance | 1 minute |
keys |
Cache Key Total Count | 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 Keys Count | This metric is used to count the number of keys deleted due to insufficient memory within the statistical period. Aggregated from the master node 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 Keys Count | This metric is used to count the number of keys deleted due to expiration within the statistical period. Aggregated from the master node 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 the master node 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 the master node 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 the master node 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 Ratio | This metric is used to count the current memory fragmentation ratio | >=0 | Redis Instance | 1 minute |
mget |
MGET | This metric is used to count the average number of mget operations per second. Aggregated from the master node 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 Channels Count | This metric is used to count the number of Pub/Sub channels. | >=0 | Redis Instance | 1 minute |
pubsub_patterns |
Pubsub Patterns 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 bytes of memory 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 the master node 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 the instance was flow-controlled within the statistical period. A value greater than 0 indicates that the current bandwidth usage exceeds the maximum bandwidth limit and is flow-controlled. Unit: Count. | >=0 | Redis Instance | 1 minute |
bandwidth_usage |
Bandwidth Utilization | This metric is used to calculate the percentage of current traffic bandwidth relative 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 for a node. Unit: us. | >=0 us | Redis Instance (Single) | 1 minute |
command_avg_rt |
Average Latency | This metric is used to count the average latency from receiving a command to sending a response for a node. Unit: us. | >=0 us | Redis Instance (Single) | 1 minute |
Redis Instance Data Node Monitoring Metrics¶
Note:
- Redis 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 Cycle (Raw 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 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 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 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 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 connections of the client. | >=0 | Redis 3.0, 4.0 Version Standby, Read-Write Separation, Cluster Instance Data Nodes | 1 minute |
client_biggest_in_buf |
Client Largest Input Buffer | This metric is used to count the maximum input data length of all existing connections of the client. Unit: Can be selected in the console, such as KB, MB, byte, etc. | >=0 | Redis 3.0, 4.0 Version 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 such as BLPOP, BRPOP, BRPOPLPUSH. | >=0 | Redis Standby, Read-Write Separation, Cluster Instance Data Nodes | 1 minute |
used_memory |
Used Memory | This metric is used to count the number of bytes of memory used by Redis. Unit: Can be selected in the console, such as KB, MB, byte, etc. | >=0 | Redis 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 memory actually 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 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 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 bytes of memory used by the Lua engine. Unit: Can be selected in the console, such as KB, MB, byte, etc. | >=0 | Redis Standby, Read-Write Separation, Cluster Instance Data Nodes | 1 minute |
memory_frag_ratio |
Memory Fragmentation Ratio | This metric is used to count the current memory fragmentation ratio. Its value is equal to used_memory_rss / used_memory. | >=0 | Redis Standby, Read-Write Separation, Cluster Instance Data Nodes | 1 minute |
total_connections_received |
New Connections Count | This metric is used to count the number of new connections within the statistical period. | >=0 | Redis Standby, Read-Write Separation, Cluster Instance Data Nodes | 1 minute |
total_commands_processed |
Processed Commands Count | This metric is used to count the number of commands processed within the statistical period. | >=0 | Redis 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 Standby, Read-Write Separation, Cluster Instance Data Nodes | 1 minute |
total_net_input_bytes |
Network Received Bytes Count | 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 Standby, Read-Write Separation, Cluster Instance Data Nodes | 1 minute |
total_net_output_bytes |
Network Sent Bytes Count | 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 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 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 Standby, Read-Write Separation, Cluster Instance Data Nodes | 1 minute |
| rejected_connections | Rejected Connections Count | This metric is used to count the number of connections rejected due to exceeding maxclients within the statistical period. | >=0 | Redis Standby, Read-Write Separation, Cluster Instance Data Nodes | 1 minute |
expired_keys |
Expired Keys Count | This metric is used to count the number of keys deleted due to expiration within the statistical period. | >=0 | Redis Standby, Read-Write Separation, Cluster Instance Data Nodes | 1 minute |
evicted_keys |
Evicted Keys Count | This metric is used to count the number of keys deleted due to insufficient memory within the statistical period. | >=0 | Redis Standby, Read-Write Separation, Cluster Instance Data Nodes | 1 minute |
pubsub_channels |
Pubsub Channels Count | This metric is used to count the number of Pub/Sub channels. | >=0 | Redis Standby, Read-Write Separation, Cluster Instance Data Nodes | 1 minute |
pubsub_patterns |
Pubsub Patterns Count | This metric is used to count the number of Pub/Sub patterns. | >=0 | Redis 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 Standby, Read-Write Separation, Cluster Instance Data Nodes | 1 minute |
command_max_delay |
Command Maximum Delay | This metric is used to count the maximum delay of commands for a node. Unit: ms. | >=0 ms | Redis Standby, Read-Write Separation, Cluster Instance Data Nodes | 1 minute |
is_slow_log_exist |
Whether Slow Log Exists | This metric is used to count whether slow logs exist for a node.Note: This monitoring does not count slow queries caused by migrate, slaveof, config, bgsave, bgrewriteaof commands. |
1: Indicates existence0: Indicates non-existence. | Redis Standby, Read-Write Separation, Cluster Instance Data Nodes | 1 minute |
keys |
Cache Key Total Count | This metric is used to count the total number of keys in the Redis cache. | >=0 | Redis 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 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 Standby, Read-Write Separation, Cluster Instance Data Nodes | 1 minute |
ms_repl_offset |
Master-Slave Data Synchronization Difference | This metric is used to count the data synchronization difference between master and slave nodes. | - | Redis 4.0, 5.0, 6.0 Version Standby, Read-Write Separation, Cluster Instance Data Nodes Slave Nodes | 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 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 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 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 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 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 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 Standby, Cluster, Redis 6.0 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 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 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 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 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 the instance was flow-controlled within the statistical period. A value greater than 0 indicates that the current bandwidth usage exceeds the maximum bandwidth limit and is flow-controlled. Unit: Count. | >=0 | Redis 4.0, 5.0, 6.0 Version 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 relative to the maximum bandwidth limit. | 0-200% | Redis 4.0, 5.0, 6.0 Version Standby, Read-Write Separation, Cluster Instance Data Nodes | 1 minute |
connections_usage |
Connection Utilization | This metric is used to calculate the percentage of current connections relative to the maximum connection limit. Unit: %. | 0-100% | Redis 4.0, 5.0, 6.0 Version 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 for a node. Unit: us. | >=0 us | Redis 4.0, 5.0, 6.0 Version 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 for a node. Unit: us. | >=0 us | Redis 4.0, 5.0, 6.0 Version 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 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 occurred within a statistical period. | >=0 | Redis 4.0, 5.0, 6.0 Version 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 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 Cycle (Raw 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 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 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 | Inbound Network 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 | Outbound Network 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 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 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 | Inbound Network 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 | Outbound Network 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 Cycle (Raw Metric) |
|---|---|---|---|---|---|
node_status |
Instance Node Status | Displays whether the Proxy node status is normal. | 0: Indicates normal1: 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 Count | 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 Count | 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 calculate the percentage of current connections relative 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 for a node. 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 for a node. 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 Cycle (Raw 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 bytes of memory 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 memory actually resident "in memory". It includes heap memory but excludes 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 Ratio | This metric is used to count the current memory fragmentation ratio. Its value is equal to used_memory_rss / used_memory. | >=0 | Memcached Instance | 1 minute |
mc_connections_received |
New Connections 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 Commands 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 Count | 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 Count | 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 Connections 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 Keys 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 Keys 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 mismatches. | >=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 Delay | This metric is used to count the maximum delay of commands. Unit: ms. | >=0ms | Memcached Instance | 1 minute |
mc_is_slow_log_exist |
Whether Slow Log Exists | 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 existence0: 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 |
Objects¶
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 billing. |
no_password_access |
String | Whether password-free access to the cache instance is allowed: true: The instance can be accessed without a password. false: The instance must be accessed through password authentication. |
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, before the cache instance status enters the running state. CREATEFAILED: The cache instance is in a failed creation state. RUNNING: The cache instance is in normal operation. RESTARTING: The cache instance is in the process of restarting. FROZEN: The cache instance is in a frozen state, and users can renew the frozen cache instance in "My Orders". EXTENDING: The cache instance is in the process of scaling up. RESTORING: The cache instance is in the process of data recovery. FLUSHING: The cache instance is in the process of data clearing. |
Note: The fields in
tags,fieldsmay change with subsequent updatesTip 1: The value of
tags.instance_idis the instance ID, used as a unique identifierTip 2: The following fields are JSON serialized strings -
fields.message-tags.az_codes