ApsaraDB for Redis monitors more than 10 groups of metrics in real time. This allows you to monitor the status of ApsaraDB for Redis instances. This topic describes the purpose of each metric.

Monitoring frequency

The monitoring frequency is the frequency at which the performance monitoring system collects monitoring data. If the system collects data every 5 seconds, the monitoring frequency is 5 Seconds, and the monitoring cycle (or collection cycle) is 5 seconds. For more information about how to modify the monitoring frequency, see Modify the monitoring frequency.

Note The default monitoring frequency is 60 Seconds. If the frequency is set to 5 Seconds, the time period between the beginning time and end time cannot exceed 30 minutes.

Monitoring group

ApsaraDB for Redis supports a wide range of monitoring groups. You can view the metrics of different kinds of monitoring groups in the console. For more information, see Customize metrics. The following table describes the features of monitoring groups.

Note Proxy nodes support only Basic Monitoring Group.
Monitoring group Description
Basic Monitoring Group The basic metrics of an instance, such as queries per second (QPS), bandwidth, and memory usage. For more information, see Metrics for data nodes in the basic monitoring group and Metrics for proxy nodes in the basic monitoring group.
Note Metrics of proxy nodes are supported by only cluster instances and read/write splitting instances.
Key Monitoring Group The metrics on the use of key-value related commands, such as the number of times DEL and EXITS are run.
String Monitoring Group The metrics on the use of string-related commands, such as the number of times APPEND and MGET are run.
Hash Monitoring Group The metrics on the use of hash-related commands, such as the number of times HGET and HDEL are run.
List Monitoring Group The metrics on the use of list-related commands, such as the number of times BLPOP and BRPOP are run.
Set Monitoring Group The metrics on the use of set-related commands, such as the number of times SADD and SCARD are run.
Zset Monitoring Group The metrics on the use of zset-related commands, such as the number of times ZADD and ZCARD are run.
HyperLog Monitoring Group The metrics on the use of HyperLogLog-related commands, such as the number of times PFADD and PFCOUNT are run.
Pub/Sub Monitoring Group The metrics on the use of publication and subscription-related commands, such as the number of times PUBLISH and SUBSCRIBE are run.
Transaction Monitoring Group The metrics on the use of transaction-related commands, such as the number of times WATCH, MULTI, and EXEC are run.
Lua Script Monitoring Group The metrics on the use of Lua script-related commands, such as the number of times EVAL and SCRIPT are run.
TairDoc monitoring group
Note This monitoring group is supported by only Performance-enhanced instances and Hybrid-storage instances of ApsaraDB for Redis Enhanced Edition.
The metrics on the use of TairDoc commands, such as the number of times JSON.SET and JSON.GET are run.
TairHash monitoring group
Note This monitoring group is supported by only Performance-enhanced instances and Hybrid-storage instances of ApsaraDB for Redis Enhanced Edition.
The metrics on the use of TairHash commands, such as the number of times EXHSET and EXHMSET are run.
TairString monitoring group
Note This monitoring group is supported by only Performance-enhanced instances and Hybrid-storage instances of ApsaraDB for Redis Enhanced Edition.
The metrics on the use of TairString commands, such as the number of times EXSET and EXGET are run.
TairGis monitoring group
Note This monitoring group is supported by only Performance-enhanced instances and Hybrid-storage instances of ApsaraDB for Redis Enhanced Edition.
The metrics on the use of TairGis commands, such as the number of times GIS.ADD, GIS.GET, and GIS.DEL are run.
TairBloom monitoring group
Note This monitoring group is supported by only Performance-enhanced instances and Hybrid-storage instances of ApsaraDB for Redis Enhanced Edition.
The metrics on the use of TairBloom commands, such as the number of times BF.RESERVE and BF.ADD are run.

Metrics for data nodes in the basic monitoring group

ApsaraDB for Redis supports multiple monitoring groups. The following table describes the metrics supported by the basic monitoring group. For read/write splitting instances and cluster instances, the metrics supported by the basic monitoring group display aggregated data. For example, the CpuUsage metric of the two types of instances displays the average CPU utilization of all nodes within an instance.

Note
  • For read/write splitting instances, the monitoring metrics of read-only read nodes are not included in aggregated metrics.
  • For read/write splitting instances, you can view the metrics of a specific node. For more information, see Query monitoring data.
Type Metric Aggregation supported Unit Description
CPU CpuUsage ✔️ % The CPU usage.
Memory UsedMemory ✔️ Bytes The amount of used memory, which includes the memory consumed by the data and cache.
memoryUsage ✔️ % The memory usage.
Note Redis 2.8 instances are not supported. To display this metric, you must upgrade the engine version of the instance. For more information, see Upgrade the major version.
Request TotalQps ✔️ Counts/s The total number of requests per second, which includes read and write requests.
ConnCount (UsedConnection) ✔️ Counts The number of used connections. This is the number of Transmission Control Protocol (TCP) connections to the node.
Note
  • This metric applies if the client is connected to a cluster instance of ApsaraDB for Redis through a direct connection.
  • This metric does not apply when the client is connected to a cluster instance or read/write splitting instance through the proxy node. In this case, take note of the number of connections to the proxy node.
GetQps ✔️ Counts/s The number of read requests per second.
Note The engine version of the ApsaraDB for Redis instance must be the latest minor version of Redis 4.0 and later. For more information, see Upgrade the major version and Upgrade the minor version.
PutQps ✔️ Counts/s The number of write requests per second.
Note The engine version of the ApsaraDB for Redis instance must be the latest minor version of Redis 4.0 and later. For more information, see Upgrade the major version and Upgrade the minor version.
ConnectionUsage ✔️ % The connections usage. Connections usage = Number of connections/Total number of connections supported by the instance.
Network IntranetIn ✔️ KBps The inbound traffic of the instance.
IntranetInRatio ✔️ % The usage rate of the inbound traffic.
IntranetOut ✔️ KBps The outbound traffic of the instance.
IntranetOutRatio ✔️ % The usage rate of the outbound traffic.
Latency AvgRt ✔️ us The average response time that is consumed by all commands. This is the average time period from the time when the data node receives the command to the time when the data node returns the result.
MaxRt ✔️ us The maximum response time of requests. This is the maximum response time at which a data node sends a response after it receives a command.
Key Keys ✔️ Counts The total number of keys.
Expires ✔️ Counts The total number of keys for which the expiration time is set.
Note This metric indicates the instantaneous value when the data is collected.
ExpiredKeys ✔️ Counts The total number of expired keys.
EvictedKeys ✔️ Counts The total number of evicted keys.
ExpiredKeysPerSecond ✔️ Counts/s The number of expired keys per second.
EvictedKeysPerSecond ✔️ Counts/s The number of evicted keys per second.
Storage DataSize
Note This monitoring group is supported by only Performance-enhanced instances and Hybrid-storage instances of ApsaraDB for Redis Enhanced Edition.
MB The size of data files, which includes the append-only files (AOF) and Redis Database (RDB) files.
LogSize
Note This monitoring group is supported by only Performance-enhanced instances and Hybrid-storage instances of ApsaraDB for Redis Enhanced Edition.
MB The size of logs, which includes the active logs of ApsaraDB for Redis instances.
swapped_key
Note This monitoring group is supported by only Hybrid-storage instances of ApsaraDB for Redis Enhanced Edition.
✔️ Counts The number of key-value pairs on the disk.
Hit hit_rate ✔️ % The hit ratio of keys. Hit ratio = Total key hits/(Total key hits + Total key misses).
Note If you use instances of Redis 2.8 and this metric is not displayed, upgrade the minor version of the instance. For more information, see Upgrade the minor version.
hit (Hit Count) ✔️ Counts The number of keys that are hit per second.
miss (Miss Count) ✔️ Counts The number of keys that are missed per second.
Key cache inmem_keys
Note This monitoring group is supported by only Hybrid-storage instances of ApsaraDB for Redis Enhanced Edition.
Counts The number of key-value pairs in memory.

Metrics for proxy nodes in the basic monitoring group

For read/write splitting instances and cluster instances, the metrics of proxy nodes display aggregated data. For example, the CpuUsage metric displays the average CPU utilization of all proxy nodes in an instance.

Note You can also view the metrics of a specific node. For more information, see Query monitoring data.
Type Metric Aggregation supported Unit Description
CPU CpuUsage ✔️ % The CPU usage.
Request TotalQps ✔️ Counts/s The total number of requests per second, which includes read and write requests.
GetQps ✔️ Counts/s The number of read requests per second.
Note To view the metric, you must upgrade the minor version of the ApsaraDB for Redis instance to the latest version. For more information, see Upgrade the minor version.
PutQps ✔️ Counts/s The number of write requests per second.
Note To view the metric, you must upgrade the minor version of the ApsaraDB for Redis instance to the latest version. For more information, see Upgrade the minor version.
Connection UsedConnection ✔️ Counts The number of used connections. This is also the number of Transmission Control Protocol (TCP) connections to the instance.
ConnectionUsage ✔️ % The connections usage. Connections usage = Number of connections/Total number of connections supported by the instance.
Network IntranetIn ✔️ KBps The inbound traffic of the instance.
IntranetOut ✔️ KBps The outbound traffic of the instance.
Latency AvgRt ✔️ us The average response time that is consumed by all commands. This is the average time period from the time when the proxy node receives the command to the time when the proxy node returns the result.
MaxRt ✔️ us The maximum response time of requests. This is the maximum response time at which a proxy node sends a response after it receives a command.
Number of bytes AvgRequestSize Byte The average number of bytes per request.
AvgResponseSize Byte The average number of bytes per response.
MaxRequestSize Byte The maximum number of bytes per request.
MaxResponseSize Byte The maximum number of bytes per response.