DCS Metrics
Introduction
This section describes DCS metrics reported to Cloud Eye as well as their namespaces and dimensions. You can use the Cloud Eye console or call APIs to query the DCS metrics and alarms.
Different types of instances are monitored on different dimensions.
Instance Type |
Instance Monitoring |
Redis Server Monitoring |
Proxy Monitoring |
---|---|---|---|
Single-node |
Supported The monitoring on the instance dimension is conducted on the Redis Server. |
N/A |
N/A |
Master/standby |
Supported The master node is monitored. |
Supported The master and standby nodes are monitored. |
N/A |
Read/write splitting |
Supported The master node is monitored. |
Supported The master and standby nodes are monitored. |
Supported Each proxy is monitored. |
Proxy Cluster |
Supported The monitoring data is the aggregated master node data. |
Supported Each shard is monitored. |
Supported Each proxy is monitored. |
Redis Cluster |
Supported The monitoring data is the aggregated master node data. |
Supported Each shard is monitored. |
N/A |
Namespace
SYS.DCS
DCS Redis 4.0/5.0/6.0 Instance Metrics
- Dimensions lists the metric dimensions.
- The monitoring data is the aggregated master node data.
- Some metrics are aggregated from the master and replica nodes. For details, see "Metric Description" in Table 2.
Metric ID |
Metric Name |
Metric Description |
Value Range |
Monitored Object |
Monitoring Period (Raw Data) |
---|---|---|---|---|---|
cpu_usage |
CPU Usage |
The monitored object's maximum CPU usage among multiple sampling values in a monitoring period Unit: % |
0–100% |
Single-node, master/standby, or read/write splitting DCS Redis instance |
1 minute |
cpu_avg_usage |
Average CPU Usage |
The monitored object's average CPU usage of multiple sampling values in a monitoring period Unit: % |
0–100% |
Single-node, master/standby, or read/write splitting DCS Redis instance |
1 minute |
command_max_delay |
Maximum Command Latency |
Maximum latency of commands Unit: ms |
≥ 0 ms |
DCS Redis instance |
1 minute |
total_connections_received |
New Connections |
Number of connections received during the monitoring period |
≥ 0 |
DCS Redis instance |
1 minute |
is_slow_log_exist |
Slow Query Logs |
Existence of slow query logs in the instance
NOTE:
Slow queries caused by the MIGRATE, SLAVEOF, CONFIG, BGSAVE, and BGREWRITEAOF commands are not counted. |
|
DCS Redis instance |
1 minute |
memory_usage |
Memory Usage |
Memory consumed by the monitored object Unit: % |
0–100% |
DCS Redis instance |
1 minute |
expires |
Keys With an Expiration |
Number of keys with an expiration in Redis |
≥ 0 |
DCS Redis instance |
1 minute |
keyspace_hits_perc |
Hit Rate |
Ratio of the number of Redis cache hits to the number of lookups. Calculation: keyspace_hits/(keyspace_hits + keyspace_misses) Aggregated from the master and replica nodes. Unit: % |
0–100% |
DCS Redis instance |
1 minute |
used_memory |
Used Memory |
Total number of bytes used by the Redis server Unit: KB, MB, or byte (configurable on the console) |
≥ 0 |
DCS Redis instance |
1 minute |
used_memory_dataset |
Used Memory Dataset |
Dataset memory that the Redis server has used Unit: KB, MB, or byte (configurable on the console) |
≥ 0 |
DCS Redis instance |
1 minute |
used_memory_dataset_perc |
Used Memory Dataset Ratio |
Percentage of dataset memory that server has used Aggregated from the master and replica nodes. Unit: % |
0–100% |
DCS Redis instance |
1 minute |
used_memory_rss |
Used Memory RSS |
Resident set size (RSS) memory that the Redis server has used, which is the memory that actually resides in the memory, including all stack and heap memory but not swapped-out memory Unit: KB, MB, or byte (configurable on the console) |
≥ 0 |
DCS Redis instance |
1 minute |
instantaneous_ops |
Ops per Second |
Number of commands processed per second |
≥ 0 |
DCS Redis instance |
1 minute |
keyspace_misses |
Keyspace Misses |
Number of failed lookups of keys in the main dictionary during the monitoring period Aggregated from the master and replica nodes. |
≥ 0 |
DCS Redis instance |
1 minute |
keys |
Keys |
Number of keys in Redis |
≥ 0 |
DCS Redis instance |
1 minute |
blocked_clients |
Blocked Clients |
Number of clients suspended by block operations |
≥ 0 |
DCS Redis instance |
1 minute |
connected_clients |
Connected Clients |
Number of connected clients. Includes connections established for system monitoring, configuration synchronization, and services. Excludes connections from replicas. |
≥ 0 |
DCS Redis instance |
1 minute |
del |
DEL |
Number of DEL commands processed per second |
0–500,000 |
DCS Redis instance |
1 minute |
evicted_keys |
Evicted Keys |
Number of keys that have been evicted and deleted during the monitoring period Aggregated from the master and replica nodes. |
≥ 0 |
DCS Redis instance |
1 minute |
expire |
EXPIRE |
Number of EXPIRE commands processed per second |
0–500,000 |
DCS Redis instance |
1 minute |
expired_keys |
Expired Keys |
Number of keys that have expired and been deleted during the monitoring period Aggregated from the master and replica nodes. |
≥ 0 |
DCS Redis instance |
1 minute |
get |
GET |
Number of GET commands processed per second Aggregated from the master and replica nodes. Unit: count/s |
0–500,000 |
DCS Redis instance |
1 minute |
hdel |
HDEL |
Number of HDEL commands processed per second |
0–500,000 |
DCS Redis instance |
1 minute |
hget |
HGET |
Number of HGET commands processed per second Aggregated from the master and replica nodes. Unit: count/s |
0–500,000 |
DCS Redis instance |
1 minute |
hmget |
HMGET |
Number of HMGET commands processed per second Aggregated from the master and replica nodes. Unit: count/s |
0–500,000 |
DCS Redis instance |
1 minute |
hmset |
HMSET |
Number of HMSET commands processed per second |
0–500,000 |
DCS Redis instance |
1 minute |
hset |
HSET |
Number of HSET commands processed per second |
0–500,000 |
DCS Redis instance |
1 minute |
instantaneous_input_kbps |
Input Flow |
Instantaneous input traffic Unit: KB/s |
≥ 0 KB/s |
DCS Redis instance |
1 minute |
instantaneous_output_kbps |
Output Flow |
Instantaneous output traffic Unit: KB/s |
≥ 0 KB/s |
DCS Redis instance |
1 minute |
memory_frag_ratio |
Memory Fragmentation Ratio |
Ratio between Used Memory RSS and Used Memory |
≥ 0 |
DCS Redis instance |
1 minute |
mget |
MGET |
Number of MGET commands processed per second Aggregated from the master and replica nodes. Unit: count/s |
0–500,000 |
DCS Redis instance |
1 minute |
mset |
MSET |
Number of MSET commands processed per second |
0–500,000 |
DCS Redis instance |
1 minute |
pubsub_channels |
PubSub Channels |
Number of Pub/Sub channels |
≥ 0 |
DCS Redis instance |
1 minute |
pubsub_patterns |
PubSub Patterns |
Number of Pub/Sub patterns |
≥ 0 |
DCS Redis instance |
1 minute |
set |
SET |
Number of SET commands processed per second |
0–500,000 |
DCS Redis instance |
1 minute |
used_memory_lua |
Used Memory Lua |
Number of bytes used by the Lua engine Unit: KB, MB, or byte (configurable on the console) |
≥ 0 |
DCS Redis instance |
1 minute |
used_memory_peak |
Used Memory Peak |
Peak memory consumed by Redis since the Redis server last started Unit: KB, MB, or byte (configurable on the console) |
≥ 0 |
DCS Redis instance |
1 minute |
sadd |
Sadd |
Number of SADD commands processed per second Unit: count/s |
0–500,000 |
DCS Redis instance |
1 minute |
smembers |
Smembers |
Number of SMEMBERS commands processed per second Aggregated from the master and replica nodes. Unit: count/s |
0–500,000 |
DCS Redis instance |
1 minute |
scan |
SCAN |
Number of SCAN operations per second Unit: count/s |
0–500,000 |
DCS Redis instance |
1 minute |
setex |
SETEX |
Number of SETEX operations per second Unit: count/s |
0–500,000 |
DCS Redis instance |
1 minute |
rx_controlled |
Flow Control Times |
Number of flow control times during the monitoring period If the value is greater than 0, the used bandwidth exceeds the upper limit and flow control is triggered. Unit: Count |
≥ 0 |
DCS Redis instance |
1 minute |
bandwidth_usage |
Bandwidth Usage |
Percentage of the used bandwidth to the maximum bandwidth limit |
0–200% |
DCS Redis instance |
1 minute |
command_max_rt |
Maximum Latency |
Maximum delay from when the node receives commands to when it responds Unit: us |
≥ 0 |
Single-node DCS Redis instance |
1 minute |
command_avg_rt |
Average Latency |
Average delay from when the node receives commands to when it responds Unit: us |
≥ 0 |
Single-node DCS Redis instance |
1 minute |
Redis Server Metrics of DCS Redis Instances
- These metrics are supported for master/standby, read/write splitting, and cluster instances.
- Dimensions lists the metric dimensions.
Metric ID |
Metric Name |
Metric Description |
Value Range |
Monitored Object |
Monitoring Period (Raw Data) |
---|---|---|---|---|---|
cpu_usage |
CPU Usage |
The monitored object's maximum CPU usage among multiple sampling values in a monitoring period Unit: % |
0–100% |
Redis Server of a master/standby, read/write splitting, or cluster DCS Redis instance |
1 minute |
cpu_avg_usage |
Average CPU Usage |
The monitored object's average CPU usage of multiple sampling values in a monitoring period Unit: % |
0–100% |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
memory_usage |
Memory Usage |
Memory consumed by the monitored object Unit: % |
0–100% |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
connected_clients |
Connected Clients |
Number of connected clients. Includes connections established for system monitoring, configuration synchronization, and services. Excludes connections from replicas |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
client_longest_out_list |
Client Longest Output List |
Longest output list among current client connections |
≥ 0 |
Redis 4.0 Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
client_biggest_in_buf |
Client Biggest Input Buf |
Maximum input data length among current client connections Unit: KB, MB, or byte (configurable on the console) |
≥ 0 |
Redis 4.0 Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
blocked_clients |
Blocked Clients |
Number of clients suspended by block operations such as BLPOP, BRPOP, and BRPOPLPUSH |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
used_memory |
Used Memory |
Total number of bytes used by the Redis server Unit: KB, MB, or byte (configurable on the console) |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
used_memory_rss |
Used Memory RSS |
RSS memory that the Redis server has used, which includes all stack and heap memory but not swapped-out memory Unit: KB, MB, or byte (configurable on the console) |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
used_memory_peak |
Used Memory Peak |
Peak memory consumed by Redis since the Redis server last started Unit: KB, MB, or byte (configurable on the console) |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
used_memory_lua |
Used Memory Lua |
Number of bytes used by the Lua engine Unit: KB, MB, or byte (configurable on the console) |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
memory_frag_ratio |
Memory Fragmentation Ratio |
Current memory fragmentation, which is the ratio between used_memory_rss/used_memory. |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
total_connections_received |
New Connections |
Number of connections received during the monitoring period |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
total_commands_processed |
Commands Processed |
Number of commands processed during the monitoring period |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
instantaneous_ops |
Ops per Second |
Number of commands processed per second |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
total_net_input_bytes |
Network Input Bytes |
Number of bytes received during the monitoring period Unit: KB, MB, or byte (configurable on the console) |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
total_net_output_bytes |
Network Output Bytes |
Number of bytes sent during the monitoring period Unit: KB, MB, or byte (configurable on the console) |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
instantaneous_input_kbps |
Input Flow |
Instantaneous input traffic Unit: KB/s |
≥ 0 KB/s |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
instantaneous_output_kbps |
Output Flow |
Instantaneous output traffic Unit: KB/s |
≥ 0 KB/s |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
rejected_connections |
Rejected Connections |
Number of connections that have exceeded maxclients and been rejected during the monitoring period |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
expired_keys |
Expired Keys |
Number of keys that have expired and been deleted during the monitoring period |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
evicted_keys |
Evicted Keys |
Number of keys that have been evicted and deleted during the monitoring period |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
pubsub_channels |
PubSub Channels |
Number of Pub/Sub channels |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
pubsub_patterns |
PubSub Patterns |
Number of Pub/Sub patterns |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
keyspace_hits_perc |
Hit Rate |
Ratio of the number of Redis cache hits to the number of lookups. Calculation: keyspace_hits/(keyspace_hits + keyspace_misses) Unit: % |
0–100% |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
command_max_delay |
Maximum Command Latency |
Maximum latency of commands Unit: ms |
≥ 0 ms |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
is_slow_log_exist |
Slow Query Logs |
Existence of slow query logs in the node
NOTE:
Slow queries caused by the MIGRATE, SLAVEOF, CONFIG, BGSAVE, and BGREWRITEAOF commands are not counted. |
|
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
keys |
Keys |
Number of keys in Redis |
≥ 0 |
Redis Server of a master/standby, read/write splitting or cluster DCS Redis instance |
1 minute |
sadd |
SADD |
Number of SADD commands processed per second Unit: count/s |
0–500,000 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
smembers |
SMEMBERS |
Number of SMEMBERS commands processed per second Unit: count/s |
0–500,000 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
ms_repl_offset |
Replication Gap |
Data synchronization gap between the master and the replica |
- |
Replica of a master/standby, read/write splitting, or cluster instance |
1 minute |
del |
DEL |
Number of DEL commands processed per second Unit: count/s |
0–500,000 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
expire |
EXPIRE |
Number of EXPIRE commands processed per second Unit: count/s |
0–500,000 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
get |
GET |
Number of GET commands processed per second Unit: count/s |
0–500,000 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
hdel |
HDEL |
Number of HDEL commands processed per second Unit: count/s |
0–500,000 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
hget |
HGET |
Number of HGET commands processed per second Unit: count/s |
0–500,000 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
hmget |
HMGET |
Number of HMGET commands processed per second Unit: count/s |
0–500,000 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
hmset |
HMSET |
Number of HMSET commands processed per second Unit: count/s |
0–500,000 |
Redis Server of a master/standby or cluster instance |
1 minute |
hset |
HSET |
Number of HSET commands processed per second Unit: count/s |
0–500,000 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
mget |
MGET |
Number of MGET commands processed per second Unit: count/s |
0–500,000 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
mset |
MSET |
Number of MSET commands processed per second Unit: count/s |
0–500,000 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
set |
SET |
Number of SET commands processed per second Unit: count/s |
0–500,000 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
rx_controlled |
Flow Control Times |
Number of flow control times during the monitoring period If the value is greater than 0, the used bandwidth exceeds the upper limit and flow control is triggered. Unit: Count |
≥ 0 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
bandwidth_usage |
Bandwidth Usage |
Percentage of the used bandwidth to the maximum bandwidth limit |
0–200% |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
connections_usage |
Connection Usage |
Percentage of the current number of connections to the maximum allowed number of connections Unit: % |
0–100% |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
command_max_rt |
Maximum Latency |
Maximum delay from when the node receives commands to when it responds Unit: us |
≥ 0 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
command_avg_rt |
Average Latency |
Average delay from when the node receives commands to when it responds Unit: us |
≥ 0 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
sync_full |
Full Sync Times |
Total number of full synchronizations since the Redis Server last started |
≥ 0 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
slow_log_counts |
Slow Queries |
Number of times that slow queries occur within a monitoring period |
≥ 0 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
scan |
SCAN |
Number of SCAN operations per second Unit: count/s |
0–500,000 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
setex |
SETEX |
Number of SETEX operations per second Unit: count/s |
0–500,000 |
Redis Server of a master/standby, read/write splitting, or cluster instance |
1 minute |
Proxy Metrics
- These metrics are supported by Proxy Cluster and read/write splitting instances.
- Dimensions lists the metric dimensions.
Metric ID |
Metric Name |
Metric Description |
Value Range |
Monitored Object |
Monitoring Period (Raw Data) |
---|---|---|---|---|---|
node_status |
Proxy Status |
Indication of whether the proxy is normal. |
|
Proxy in a Proxy Cluster or read/write splitting instance |
1 minute |
cpu_usage |
CPU Usage |
The monitored object's maximum CPU usage among multiple sampling values in a monitoring period Unit: % |
0–100% |
Proxy in a Proxy Cluster or read/write splitting instance |
1 minute |
cpu_avg_usage |
Average CPU Usage |
The monitored object's average CPU usage of multiple sampling values in a monitoring period Unit: % |
0–100% |
Proxy in a Proxy Cluster or read/write splitting instance |
1 minute |
memory_usage |
Memory Usage |
Memory consumed by the monitored object Unit: % |
0–100% |
Proxy in a Proxy Cluster or read/write splitting instance |
1 minute |
connected_clients |
Connected Clients |
Number of connected clients. Includes connections established for system monitoring, configuration synchronization, and services. Excludes connections from replicas |
≥ 0 |
Proxy in a Proxy Cluster or read/write splitting instance |
1 minute |
instantaneous_ops |
Ops per Second |
Number of commands processed per second |
≥ 0 |
Proxy in a Proxy Cluster or read/write splitting instance |
1 minute |
instantaneous_input_kbps |
Input Flow |
Instantaneous input traffic Unit: KB/s |
≥ 0 KB/s |
Proxy in a Proxy Cluster or read/write splitting instance |
1 minute |
instantaneous_output_kbps |
Output Flow |
Instantaneous output traffic Unit: KB/s |
≥ 0 KB/s |
Proxy in a Proxy Cluster or read/write splitting instance |
1 minute |
total_net_input_bytes |
Network Input Bytes |
Number of bytes received during the monitoring period Unit: KB, MB, or byte (configurable on the console) |
≥ 0 |
Proxy in a Proxy Cluster or read/write splitting instance |
1 minute |
total_net_output_bytes |
Network Output Bytes |
Number of bytes sent during the monitoring period Unit: KB, MB, or byte (configurable on the console) |
≥ 0 |
Proxy in a Proxy Cluster or read/write splitting instance |
1 minute |
connections_usage |
Connection Usage |
Percentage of the current number of connections to the maximum allowed number of connections Unit: % |
0–100% |
Proxy in a Proxy Cluster or read/write splitting instance |
1 minute |
command_max_rt |
Maximum Latency |
Maximum delay from when the node receives commands to when it responds Unit: us |
≥ 0 |
Proxy in a Proxy Cluster or read/write splitting instance |
1 minute |
command_avg_rt |
Average Latency |
Average delay from when the node receives commands to when it responds Unit: us |
≥ 0 |
Proxy in a Proxy Cluster or read/write splitting instance |
1 minute |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.