TencentDB for Redis provides a complete and easy-to-use monitoring service where you don’t have to worry about, for example, collecting monitoring data or OPS of the monitoring system. The monitoring service includes Proxy monitoring, Redis monitoring, and instance monitoring which summarizes the monitoring data of an entire instance.
InstanceSet.MonitorVersion
field returned by the DescribeInstances API. If the value is 5s
, this instance supports the monitoring granularity of five seconds; if the value is 1m
, it supports only the monitoring granularity of one minute.TencentDB for Redis currently supports monitoring metrics at the five-second, one-minute, five-minutes, one-hour, or one-day granularity. For the retention period of monitoring data at each granularity, please see Use Limits.
You can view TencentDB for Redis monitoring information in the instance list and on the instance monitoring page in the TencentDB for Redis console, or in the Cloud Monitor console.
Each TencentDB for Redis instance contains at least 3 Proxy nodes. Generally, the number of Proxy nodes is 1.5 times that of Redis nodes. The Proxy node supports the following monitoring metrics:
Category | Metric | Parameter | Unit | Description |
---|---|---|---|---|
CPU | CPU utilization | cpu_util | % | Proxy CPU utilization |
Request | Total requests | proxy_commands | requests/second | The number of proxy command executions per second |
Key requests | cmd_key_count | keys/second | The number of keys accessed by a command per second | |
Mget requests | cmd_mget | requests/second | The number of Mget command executions per second | |
Execution errors | cmd_err | errors/second | The number of Proxy command execution errors per second. For example, the command does not exist, parameters are incorrect, etc. | |
Big value requests | cmd_big_value | requests/second | The number of executions of requests larger than 32 KB per second | |
Network | Connections | connections | - | The number of TCP connections to an instance |
Connection utilization | connections_util | % | The ratio of the number of TCP connections to the maximum number of connections | |
Inbound traffic | in_flow | MB/s | Private inbound traffic | |
Inbound traffic utilization | in_bandwidth_util | % | The ratio of the actually used private inbound traffic to the maximum traffic | |
Inbound traffic limit count | in_flow_limit | - | The number of times inbound traffic triggers a traffic limit | |
Outbound traffic | out_flow | MB/s | Private outbound traffic | |
Outbound traffic utilization | out_bandwidth_util | % | The ratio of the actually used private outbound traffic to the maximum traffic | |
Outbound traffic limit count | out_flow_limit | - | The number of times outbound traffic triggers a traffic limit | |
Latency | Average execution latency | latency_avg | ms | The average execution latency between the proxy and the Redis server |
Maximum execution latency | latency_max | ms | The maximum execution latency between the proxy and the Redis server | |
Average read latency | latency_read | ms | The average execution latency of read commands between the proxy and the Redis server. For more information about read command types, please see Command types. | |
Average write latency | latency_write | ms | The average execution latency of write commands between the proxy and the Redis server. For more information about write command types, please see Command types. | |
Average latency of other commands | latency_other | ms | The average execution latency of commands (excluding write and read commands) between the proxy and the Redis server |
The Redis node monitoring includes monitoring information of all master nodes and replica nodes in an instance or a cluster. The following monitoring metrics are supported:
Category | Metric | Parameter | Unit | Description |
---|---|---|---|---|
CPU | CPU utilization | cpu_util | % | Average CPU utilization |
Network | Connections | connections | - | The number of connections between the proxy and a node |
Connection utilization | connections_util | % | The connection utilization of a node | |
Memory | Used memory | mem_used | MB | Actually used memory capacity, including the capacity for data and cache |
Memory utilization | mem_util | % | The ratio of the actually used memory to the requested total memory | |
Total keys | keys | - | The total number of keys (level-1 keys) in instance storage | |
Expired keys | expired | - | The number of keys expired in a time window, which is equal to the value of `expired_keys` outputted by the `info` command | |
Evicted keys | evicted | - | The number of keys evicted in a time window, which is equal to the value of `evicted_keys` outputted by the `info` command | |
Replication delay | repl_delay | Byte | The command delay between the replica node and the master node | |
Request | Total requests | commands | requests/second | QPS, that is, the number of command executions per second |
Read requests | cmd_read | requests/second | The number of read command executions per second. For more information about read command types, please see Command types. | |
Write requests | cmd_write | requests/second | The number of write command executions per second. For more information about write command types, please see Command types. | |
Other requests | cmd_other | requests/second | The number of command (excluding write and read commands) executions per second | |
Response | Slow queries | cmd_slow | - | The number of command executions with a latency greater than the `slowlog\-log\-slower\-than` configuration |
Read request hits | cmd_hits | - | The number of keys successfully requested by read commands, which is equal to the value of the `keyspace_hits` metric output by the `info` command | |
Read request misses | cmd_miss | - | The number of keys unsuccessfully requested by read commands, which is equal to the value of the `keyspace_misses` metric output by the `info` command | |
Read request hit rate | cmd_hits_ratio | % | Key hits/(Key hits + Key misses). This metric reflects cache misses. |
The instance monitoring includes all monitoring data of an instance, including the monitoring data of Proxy nodes and Redis nodes, which is aggregated by the SUM, AVG, MAX, and LAST algorithms.
Category | Metric | Associated Node View | Parameter | Unit | Description |
---|---|---|---|---|---|
CPU | CPU utilization | Redis node | cpu_util | % | Average CPU utilization |
Maximum node CPU utilization | Redis node | cpu_max_util | % | The maximum among all node (shard or replica) CPU utilizations in an instance | |
Memory | Used memory | Redis node | mem_used | MB | Actually used memory capacity, including the capacity for data and cache |
Memory utilization | Redis node | mem_util | % | The ratio of the actually used memory to the requested total memory | |
Maximum node memory utilization | Redis node | mem_max_util | % | The maximum among all node (shard or replica) memory utilizations in an instance | |
Total keys | Redis node | keys | - | The total number of keys (level-1 keys) in instance storage | |
Expired keys | Redis node | expired | - | The number of keys expired in a time window, which is equal to the value of `expired_keys` outputted by the `info` command | |
Evicted keys | Redis node | evicted | - | The number of keys evicted in a time window, which is equal to the value of `evicted_keys` outputted by the `info` command | |
Network | Connections | Proxy node | connections | - | The number of TCP connections to an instance |
Connection utilization | Proxy node | connections_util | % | The ratio of the number of TCP connections to the maximum number of connections | |
Inbound traffic | Proxy node | in_flow | MB/s | Private inbound traffic | |
Inbound traffic utilization | Proxy node | in_bandwidth_util | % | The ratio of the actually used private inbound traffic to the maximum traffic | |
Inbound traffic limit count | Proxy node | in_flow_limit | - | The number of times inbound traffic triggers a traffic limit | |
Outbound traffic | Proxy node | out_flow | MB/s | Private outbound traffic | |
Outbound traffic utilization | Proxy node | out_bandwidth_util | % | The ratio of the actually used private outbound traffic to the maximum traffic | |
Outbound traffic limit count | Proxy node | out_flow_limit | - | The number of times outbound traffic triggers a traffic limit | |
Average execution latency | Proxy node | latency_avg | ms | The average execution latency between the proxy and the Redis server | |
Maximum execution latency | Proxy node | latency_max | ms | The maximum execution latency between the proxy and the Redis server | |
Average read latency | Proxy node | latency_read | ms | The average execution latency of read commands between the proxy and the Redis server. For more information about read command types, please see Command types. | |
Average write latency | Proxy node | latency_write | ms | The average execution latency of write commands between the proxy and the Redis server. For more information about write command types, please see Command types. | |
Average latency of other commands | Proxy node | latency_other | ms | The average execution latency of commands (excluding write and read commands) between the proxy and the Redis server | |
Request | Total requests | Redis node | commands | requests/second | QPS, that is, the number of command executions per second |
Read requests | Redis node | cmd_read | requests/second | The number of read command executions per second. For more information about read command types, please see Command types. | |
Write requests | Redis node | cmd_write | requests/second | The number of write command executions per second. For more information about write command types, please see Command types. | |
Other requests | Redis node | cmd_other | requests/second | The number of command (excluding write and read commands) executions per second | |
Big value requests | Proxy node | cmd_big_value | requests/second | The number of executions of commands larger than 32 KB per second | |
Key requests | Proxy node | cmd_key_count | keys/second | The number of keys accessed by a command per second | |
Mget requests | Proxy node | cmd_mget | requests/second | The number of Mget command executions per second | |
Slow queries | Redis node | cmd_slow | - | The number of command executions with a latency greater than the `slowlog\-log\-slower\-than` configuration | |
Read request hits | Redis node | cmd_hits | - | The number of keys successfully requested by read commands, which is equal to the value of the `keyspace_hits` metric output by the `info` command | |
Read request misses | Redis node | cmd_miss | - | The number of keys unsuccessfully requested by read commands, which is equal to the value of the `keyspace_misses` metric output by the `info` command | |
Execution errors | Proxy node | cmd_err | - | The number of command execution errors. For example, the command does not exist, parameters are incorrect, etc. | |
Read request hit rate | Redis node | cmd_hits_ratio | % | Key hits/(Key hits + Key misses). This metric reflects cache misses. |
Type | Commands |
---|---|
Read command | get, strlen, exists, getbit, getrange, substr, mget, llen, lindex, lrange, sismember, scard, srandmember, sinter, sunion, sdiff, smembers, sscan, zrange, zrangebyscore, zrevrangebyscore, zrangebylex, zrevrangebylex, zcount, zlexcount, zrevrange, zcard, zscore, zrank, zrevrank, zscan, hget, hmget, hlen, hstrlen, hkeys, hvals, hgetall, hexists, hscan, randomkey, keys, scan, dbsize, type, ttl, touch, pttl, dump, object, memory, bitcount, bitpos, georadius_ro, georadiusbymember_ro, geohash, geopos, geodist, pfcount |
Write command | set, setnx, setex, psetex, append, del, unlink, setbit, bitfield, setrange, incr, decr, rpush, lpush, rpushx, lpushx, linsert, rpop, lpop, brpop, brpoplpush, blpop, lset, ltrim, lrem, rpoplpush, sadd, srem, smove, spop, sinterstore, sunionstore, sdiffstore, zadd, zincrby, zrem, zremrangebyscore, zremrangebyrank, zremrangebylex, zunionstore, zinterstore, hset, hsetnx, hmset, hincrby, hincrbyfloat, hdel, incrby, decrby, incrbyfloat, getset, mset, msetnx, swapdb, move, rename, renamenx, expire, expireat, pexpire, pexpireat, flushdb, flushall, sort, persist, restore, restore-asking, migrate, bitop, geoadd, georadius, georadiusbymember, pfadd, pfmerge, pfdebug |
Use the DescribeInstanceNodeInfo API to get the IDs of Proxy nodes and Redis nodes.
Note:
The IDs of Proxy and Redis nodes will change when node failover, instance capacity expansion/reduction, data migration, etc., occur. Therefore, we recommend that you get the latest node information from the API in a timely manner.
Was this page helpful?