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.
- Single-node:
Single-node instances are monitored on the instance dimension. The monitoring is conducted on the Redis Server.
- Master/standby:
Master/Standby instances are monitored on the instance and Redis Server dimensions. Instance monitoring covers the master node, while Redis Server monitoring covers the master and standby nodes.
- Cluster:
Proxy Cluster instances are monitored on the instance, Redis Server, and proxy dimensions. Instance monitoring covers the aggregated master node data, Redis Server monitoring covers each shard in the cluster, and proxy monitoring covers each proxy in the cluster.
Redis Cluster instances are monitored on the instance and Redis Server dimensions. Instance monitoring covers the aggregated master node data and Redis Server monitoring covers each shard in the cluster.
Namespace
SYS.DCS
DCS Redis 3.0 Instance Metrics
The Monitored Objects and Dimensions column lists instances and dimensions that support the corresponding metrics.
Metric ID |
Metric |
Description |
Value Range |
Monitored Object and Dimension |
Monitoring Period (Raw Data) |
---|---|---|---|---|---|
cpu_usage |
CPU Usage |
CPU consumed by the monitored object Unit: % |
0–100% |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
memory_usage |
Memory Usage |
Memory consumed by the monitored object Unit: % |
0–100% |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
net_in_throughput |
Network Input Throughput |
Inbound throughput per second on a port Unit: byte/s |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
net_out_throughput |
Network Output Throughput |
Outbound throughput per second on a port Unit: byte/s |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
connected_clients |
Connected Clients |
Number of connected clients (excluding those from slave nodes) |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
client_longest_out_list |
Client Longest Output List |
Longest output list among current client connections |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
client_biggest_in_buf |
Client Biggest Input Buf |
Maximum input data length among current client connections Unit: byte |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
blocked_clients |
Blocked Clients |
Number of clients suspended by block operations such as BLPOP, BRPOP, and BRPOPLPUSH |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
used_memory |
Used Memory |
Number of bytes used by the Redis server Unit: byte |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
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: byte |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
used_memory_peak |
Used Memory Peak |
Peak memory consumed by Redis since the Redis server last started Unit: byte |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
used_memory_lua |
Used Memory Lua |
Number of bytes used by the Lua engine Unit: byte |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
memory_frag_ratio |
Memory Fragmentation Ratio |
Current memory fragmentation, which is the ratio between used_memory_rss/used_memory. |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
total_connections_received |
New Connections |
Number of connections received during the monitoring period |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
total_commands_processed |
Commands Processed |
Number of commands processed during the monitoring period |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
instantaneous_ops |
Ops per Second |
Number of commands processed per second |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
total_net_input_bytes |
Network Input Bytes |
Number of bytes received during the monitoring period Unit: byte |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
total_net_output_bytes |
Network Output Bytes |
Number of bytes sent during the monitoring period Unit: byte |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
instantaneous_input_kbps |
Input Flow |
Instantaneous input traffic Unit: kbit/s |
≥ 0 kbits/s |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
instantaneous_output_kbps |
Output Flow |
Instantaneous output traffic Unit: kbit/s |
≥ 0 kbits/s |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
rejected_connections |
Rejected Connections |
Number of connections that have exceeded maxclients and been rejected during the monitoring period |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
expired_keys |
Expired Keys |
Number of keys that have expired and been deleted during the monitoring period |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
evicted_keys |
Evicted Keys |
Number of keys that have been evicted and deleted during the monitoring period |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
keyspace_hits |
Keyspace Hits |
Number of successful lookups of keys in the main dictionary during the monitoring period |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
keyspace_misses |
Keyspace Misses |
Number of failed lookups of keys in the main dictionary during the monitoring period |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
pubsub_channels |
PubSub Channels |
Number of Pub/Sub channels |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
pubsub_patterns |
PubSub Patterns |
Number of Pub/Sub patterns |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
keyspace_hits_perc |
Hit Rate |
Ratio of the number of Redis cache hits to the number of lookups Unit: % |
0–100% |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
command_max_delay |
Maximum Command Latency |
Maximum latency of commands Unit: ms |
≥ 0 ms |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
auth_errors |
Authentication Failures |
Number of failed authentications |
≥ 0 |
Monitored object: Single-node or master/standby DCS Redis instance Dimension: dcs_instance_id |
1 minute |
is_slow_log_exist |
Slow Query Logs |
Existence of slow query logs in the instance |
|
Monitored object: Single-node or master/standby DCS Redis instance Dimension: dcs_instance_id |
1 minute |
keys |
Keys |
Number of keys in Redis |
≥ 0 |
Monitored object: Single-node or master/standby DCS Redis instance Dimension: dcs_instance_id |
1 minute |
DCS Redis 4.0 and 5.0 Instance Metrics
The Monitored Objects and Dimensions column lists instances and dimensions that support the corresponding metrics.
Metric ID |
Metric |
Description |
Value Range |
Monitored Object and Dimension |
Monitoring Period (Raw Data) |
---|---|---|---|---|---|
cpu_usage |
CPU Usage |
CPU consumed by the monitored object Unit: % |
0–100% |
Monitored object: Single-node or master/standby DCS Redis instance Dimension: dcs_instance_id |
1 minute |
command_max_delay |
Maximum Command Latency |
Maximum latency of commands Unit: ms |
≥ 0 ms |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
total_connections_received |
New Connections |
Number of connections received during the monitoring period |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
is_slow_log_exist |
Slow Query Logs |
Existence of slow query logs in the instance |
|
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
memory_usage |
Memory Usage |
Memory consumed by the monitored object Unit: % |
0–100% |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
expires |
Keys With an Expiration |
Number of keys with an expiration in Redis |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
keyspace_hits_perc |
Hit Rate |
Ratio of the number of Redis cache hits to the number of lookups Unit: % |
0–100% |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
used_memory |
Used Memory |
Number of bytes used by the Redis server Unit: byte |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
used_memory_dataset |
Used Memory Dataset |
Dataset memory that the Redis server has used Unit: byte |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
used_memory_dataset_perc |
Used Memory Dataset Ratio |
Percentage of dataset memory that the Redis server has used Unit: % |
0–100% |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
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: byte |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
instantaneous_ops |
Ops per Second |
Number of commands processed per second |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
keyspace_misses |
Keyspace Misses |
Number of failed lookups of keys in the main dictionary during the monitoring period |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
keys |
Keys |
Number of keys in Redis |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
blocked_clients |
Blocked Clients |
Number of clients suspended by block operations |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
connected_clients |
Connected Clients |
Number of connected clients (excluding those from slave nodes) |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
del |
DEL |
Number of DEL commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
evicted_keys |
Evicted Keys |
Number of keys that have been evicted and deleted during the monitoring period |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
expire |
EXPIRE |
Number of EXPIRE commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
expired_keys |
Expired Keys |
Number of keys that have expired and been deleted during the monitoring period |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
get |
GET |
Number of GET commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
hdel |
HDEL |
Number of HDEL commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
hget |
HGET |
Number of HGET commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
hmget |
HMGET |
Number of HMGET commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
hmset |
HMSET |
Number of HMSET commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
hset |
HSET |
Number of HSET commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
instantaneous_input_kbps |
Input Flow |
Instantaneous input traffic Unit: KB/s |
≥ 0 KB/s |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
instantaneous_output_kbps |
Output Flow |
Instantaneous output traffic Unit: KB/s |
≥ 0 KB/s |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
memory_frag_ratio |
Memory Fragmentation Ratio |
Ratio between Used Memory RSS and Used Memory |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
mget |
MGET |
Number of MGET commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
mset |
MSET |
Number of MSET commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
pubsub_channels |
PubSub Channels |
Number of Pub/Sub channels |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
pubsub_patterns |
PubSub Patterns |
Number of Pub/Sub patterns |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
set |
SET |
Number of SET commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
used_memory_lua |
Used Memory Lua |
Number of bytes used by the Lua engine Unit: byte |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
used_memory_peak |
Used Memory Peak |
Peak memory consumed by Redis since the Redis server last started Unit: byte |
≥ 0 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
sadd |
Sadd |
Number of SADD commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
smembers |
Smembers |
Number of SMEMBERS commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Single-node, master/standby, or cluster DCS Redis instance Dimension: dcs_instance_id |
1 minute |
rx_controlled |
Flow Control Times |
Number of flow control times during the monitoring period Unit: Count |
≥ 0 |
Monitored object: Redis Cluster instance Dimension: dcs_instance_id |
1 minute |
bandwidth_usage |
Bandwidth Usage |
Percentage of the used bandwidth to the maximum bandwidth limit |
0–200% |
Monitored object: Redis Cluster instance Dimension: dcs_instance_id |
1 minute |
Cluster DCS Redis Instance Metrics
- The following describes the metrics for cluster DCS instances. For Proxy Cluster DCS Redis 3.0 instances, the monitoring covers Redis Servers and Proxies. For Redis Cluster DCS Redis 4.0 and 5.0 instances, the monitoring only covers Redis Servers. For details, see Table 3 and Table 4.
- The Monitored Objects and Dimensions column lists instances and dimensions that support the corresponding metrics.
Metric ID |
Metric |
Description |
Value Range |
Monitored Object and Dimension |
Monitoring Period (Raw Data) |
---|---|---|---|---|---|
cpu_usage |
CPU Usage |
CPU consumed by the monitored object Unit: % |
0–100% |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
memory_usage |
Memory Usage |
Memory consumed by the monitored object Unit: % |
0–100% |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
connected_clients |
Connected Clients |
Number of connected clients (excluding those from slave nodes) |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
client_longest_out_list |
Client Longest Output List |
Longest output list among current client connections |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
client_biggest_in_buf |
Client Biggest Input Buf |
Maximum input data length among current client connections Unit: byte |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
blocked_clients |
Blocked Clients |
Number of clients suspended by block operations such as BLPOP, BRPOP, and BRPOPLPUSH |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
used_memory |
Used Memory |
Number of bytes used by the Redis server Unit: byte |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
used_memory_rss |
Used Memory RSS |
RSS memory that the Redis server has used, which including all stack and heap memory but not swapped-out memory Unit: byte |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
used_memory_peak |
Used Memory Peak |
Peak memory consumed by Redis since the Redis server last started Unit: byte |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
used_memory_lua |
Used Memory Lua |
Number of bytes used by the Lua engine Unit: byte |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
memory_frag_ratio |
Memory Fragmentation Ratio |
Current memory fragmentation, which is the ratio between used_memory_rss/used_memory. |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
total_connections_received |
New Connections |
Number of connections received during the monitoring period |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
total_commands_processed |
Commands Processed |
Number of commands processed during the monitoring period |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
instantaneous_ops |
Ops per Second |
Number of commands processed per second |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
total_net_input_bytes |
Network Input Bytes |
Number of bytes received during the monitoring period Unit: byte |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
total_net_output_bytes |
Network Output Bytes |
Number of bytes sent during the monitoring period Unit: byte |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
instantaneous_input_kbps |
Input Flow |
Instantaneous input traffic Unit: KB/s |
≥ 0 KB/s |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
instantaneous_output_kbps |
Output Flow |
Instantaneous output traffic Unit: KB/s |
≥ 0 KB/s |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
rejected_connections |
Rejected Connections |
Number of connections that have exceeded maxclients and been rejected during the monitoring period |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
expired_keys |
Expired Keys |
Number of keys that have expired and been deleted during the monitoring period |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
evicted_keys |
Evicted Keys |
Number of keys that have been evicted and deleted during the monitoring period |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
pubsub_channels |
PubSub Channels |
Number of Pub/Sub channels |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
pubsub_patterns |
PubSub Patterns |
Number of Pub/Sub patterns |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
keyspace_hits_perc |
Hit Rate |
Ratio of the number of Redis cache hits to the number of lookups Unit: % |
0–100% |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
command_max_delay |
Maximum Command Latency |
Maximum latency of commands Unit: ms |
≥ 0 ms |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
is_slow_log_exist |
Slow Query Logs |
Existence of slow query logs in the node |
|
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
keys |
Keys |
Number of keys in Redis |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
sadd |
Sadd |
Number of SADD commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Redis Server of cluster DCS Redis 3.0, 4.0, or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
smembers |
Smembers |
Number of SMEMBERS commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Redis Server of cluster DCS Redis 4.0 or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
ms_repl_offset |
Replication Gap |
Data synchronization gap between the master and the replica |
- |
Monitored object: Replica of cluster DCS Redis 4.0 or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
del |
DEL |
Number of DEL commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Redis Server of cluster DCS Redis 4.0 or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
expire |
EXPIRE |
Number of EXPIRE commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Redis Server of cluster DCS Redis 4.0 or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
get |
GET |
Number of GET commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Redis Server of cluster DCS Redis 4.0 or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
hdel |
HDEL |
Number of HDEL commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Redis Server of cluster DCS Redis 4.0 or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
hget |
HGET |
Number of HGET commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Redis Server of cluster DCS Redis 4.0 or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
hmget |
HMGET |
Number of HMGET commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Redis Server of cluster DCS Redis 4.0 or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
hmset |
HMSET |
Number of HMSET commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Redis Server of cluster DCS Redis 4.0 or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
hset |
HSET |
Number of HSET commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Redis Server of cluster DCS Redis 4.0 or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
mget |
MGET |
Number of MGET commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Redis Server of cluster DCS Redis 4.0 or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
mset |
MSET |
Number of MSET commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Redis Server of cluster DCS Redis 4.0 or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
set |
SET |
Number of SET commands processed per second Unit: Count/s |
0–500,000 |
Monitored object: Redis Server of cluster DCS Redis 4.0 or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
rx_controlled |
Flow Control Times |
Number of flow control times during the monitoring period Unit: Count |
≥ 0 |
Monitored object: Redis Server of cluster DCS Redis 4.0 or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
bandwidth_usage |
Bandwidth Usage |
Percentage of the used bandwidth to the maximum bandwidth limit |
0–200% |
Monitored object: Redis Server of cluster DCS Redis 4.0 or 5.0 instance Dimension: dcs_cluster_redis_node |
1 minute |
Metric ID |
Metric |
Description |
Value Range |
Monitored Object and Dimension |
Monitoring Period (Raw Data) |
---|---|---|---|---|---|
cpu_usage |
CPU Usage |
CPU consumed by the monitored object Unit: % |
0–100% |
Monitored object: Proxy in a DCS Redis 3.0 instance Dimension: dcs_cluster_proxy_node |
1 minute |
memory_usage |
Memory Usage |
Memory consumed by the monitored object Unit: % |
0–100% |
Monitored object: Proxy in a DCS Redis 3.0 instance Dimension: dcs_cluster_proxy_node |
1 minute |
p_connected_clients |
Connected Clients |
Number of connected clients |
≥ 0 |
Monitored object: Proxy in a DCS Redis 3.0 instance Dimension: dcs_cluster_proxy_node |
1 minute |
max_rxpck_per_sec |
Max. NIC Data Packet Receive Rate |
Maximum number of data packets received by the proxy NIC per second during the monitoring period Unit: packages/second |
0–10,000,000 |
Monitored object: Proxy in a DCS Redis 3.0 instance Dimension: dcs_cluster_proxy_node |
1 minute |
max_txpck_per_sec |
Max. NIC Data Packet Transmit Rate |
Maximum number of data packets transmitted by the proxy NIC per second during the monitoring period Unit: packages/second |
0–10,000,000 |
Monitored object: Proxy in a DCS Redis 3.0 instance Dimension: dcs_cluster_proxy_node |
1 minute |
max_rxkB_per_sec |
Maximum Inbound Bandwidth |
Largest volume of data received by the proxy NIC per second Unit: KB/s |
≥ 0 KB/s |
Monitored object: Proxy in a DCS Redis 3.0 instance Dimension: dcs_cluster_proxy_node |
1 minute |
max_txkB_per_sec |
Maximum Outbound Bandwidth |
Largest volume of data transmitted by the proxy NIC per second Unit: KB/s |
≥ 0 KB/s |
Monitored object: Proxy in a DCS Redis 3.0 instance Dimension: dcs_cluster_proxy_node |
1 minute |
avg_rxpck_per_sec |
Average NIC Data Packet Receive Rate |
Average number of data packets received by the proxy NIC per second during the monitoring period Unit: packages/second |
0–10,000,000 |
Monitored object: Proxy in a DCS Redis 3.0 instance Dimension: dcs_cluster_proxy_node |
1 minute |
avg_txpck_per_sec |
Average NIC Data Packet Transmit Rate |
Average number of data packets transmitted by the proxy NIC per second during the monitoring period Unit: packages/second |
0–10,000,000 |
Monitored object: Proxy in a DCS Redis 3.0 instance Dimension: dcs_cluster_proxy_node |
1 minute |
avg_rxkB_per_sec |
Average Inbound Bandwidth |
Average volume of data received by the proxy NIC per second Unit: KB/s |
≥ 0 KB/s |
Monitored object: Proxy in a DCS Redis 3.0 instance Dimension: dcs_cluster_proxy_node |
1 minute |
avg_txkB_per_sec |
Average Outbound Bandwidth |
Average volume of data transmitted by the proxy NIC per second Unit: KB/s |
≥ 0 KB/s |
Monitored object: Proxy in a DCS Redis 3.0 instance Dimension: dcs_cluster_proxy_node |
1 minute |
Dimensions
Key |
Value |
---|---|
dcs_instance_id |
DCS Redis instance |
dcs_cluster_redis_node |
Redis Server |
dcs_cluster_proxy_node |
Proxy |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot