Monitoring Feature

Last updated: 2020-02-19 18:42:19

    TencentDB for Redis provides a full range of monitoring and custom alarming capabilities, including metrics such as load monitoring, access statistics, and network traffic.
    The monitoring data is collected by the agents deployed on each host and then reported to the data relay node where it is checked, summarized, and reported to the Cloud Monitor system in batches. Cloud Monitor provides data views, data query APIs, and custom alarms.

    You can log in to the Redis Console or Cloud Monitor Console to view monitoring data.

    Monitoring Data Retention Period

    Redis currently supports monitoring metrics at the 1-minute, 5-minutes, 1-hour, or 1-day granularity. For the retention period of monitoring data at each granularity, please see Use Limits.

    Descriptions of Monitoring Metrics

    Cloud Monitor provides the following monitoring metrics for TencentDB for Redis instances:

    Category Name Parameter Unit Description
    CPU CPU utilization cpu_us_min % Average CPU utilization
    Memory Memory usage storage_min MB Memory capacity actually used, including data and cache
    Content utilization storage_us_min % The ratio of the memory actually used to the total memory requested
    Keys keys_min - Total number of keys stored in an instance (first-level keys)
    Expired keys expired_keys_min - Number of keys eliminated in a time window, which corresponds to the `expired_keys` output by the `info` command
    Evicted keys evicted_keys_min - Number of keys evicted in a time window, which corresponds to the `evicted_keys` output by the `info` command
    Network Connections connections_min - Number of TCP connections to an instance
    Connection utilization connections_us_min % Proportion of used connections
    Inbound traffic in_flow_min Mb/s Private network inbound traffic
    Inbound traffic utilization in_flow_us_min % Proportion of used private network inbound traffic
    Outbound traffic out_flow_min Mb/s Private network outbound traffic
    Outbound traffic utilization out_flow_us_min % Proportion of used private network outbound traffic
    Latency Average execution latency latency_min ms Average execution latency from proxy to Redis server
    Average read latency latency_get_min ms Average execution latency of read commands from proxy to Redis server
    Average write latency latency_set_min ms Average execution latency of write command from proxy to Redis server
    Average latency of other commands latency_other_min ms Average execution latency of commands other than read and write commands from proxy to Redis server
    Request Requests qps_min requests/second QPS, i.e., command executions
    Read requests stat_get_min requests/second Read command executions
    Write requests stat_set_min requests/second Write command executions
    Other requests stat_other_min requests/second Executions of commands other than read and write commands
    Big value requests big_value_min requests/second Number of executions for which the request size exceeds 32 KB
    Response Slow queries slow_query_min - Number of slow query commands
    Read request hits stat_success_min - Number of existing read request keys, which corresponds to the `keyspace_hits` metric output by the `info` command
    Read request misses stat_missed_min - Number of non-existing read request keys, which corresponds to the `keyspace_misses` metric output by the `info` command
    Execution errors cmd_err_min - Number of command execution errors, such as when a command does not exist or a parameter is incorrect
    Read request hit rate cache_hit_ratio_min % Key hits/(key hits + key misses). This metric can reflect the situation of cache miss. When the access request quantity is 0, the value of this metric will be null

    The monitoring information of the Redis Cluster Edition can be divided into summary and shard information. The shard information does not include the network and latency metrics, while the summary information includes two additional metrics:

    Category Name Parameter Unit Description
    CPU Maximum shard CPU utilization cpu_max_us_min % The highest CPU utilization value of all shards in a cluster
    Memory Maximum shard memory utilization storage_max_us_min % The highest memory utilization value of all shards in a cluster

    Command category

    Command Category List
    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

    Was this page helpful?

    Was this page helpful?

    • Not at all
    • Not very helpful
    • Somewhat helpful
    • Very helpful
    • Extremely helpful
    Send Feedback
    Help