Technologies/Redis/redis.commands.calls
RedisRedisMetric

redis.commands.calls

Total number of calls for a specific command
Dimensions:None
Available on:Native (1)

Summary

Cumulative counter tracking the total number of Redis commands processed since server startup across all command types. The rate of change indicates current throughput (operations per second). Sudden drops suggest client connectivity issues or application failures, while steady increases confirm normal operation. Compare with redis.commands.usec to identify periods where throughput increases but per-command latency also rises, indicating resource saturation.

Interface Metrics (1)
Native
Total number of calls for a specific command
Dimensions:None
Sources
redis.commands.callsredis.io
Related Insights (2)
Blocked Clients Indicate Synchronous Operation Bottleneckwarning

Increasing redis.clients.blocked count indicates clients waiting on blocking operations (BLPOP, BRPOP, BRPOPLPUSH, BLMOVE, BZPOPMIN, BZPOPMAX), which can cause connection pool exhaustion if client timeouts are too long or if producers aren't keeping up with consumers.

▸
Command Latency Spikes from Expensive O(N) Operationswarning

Certain Redis commands have O(N) complexity (KEYS, SMEMBERS, HGETALL, LRANGE without limit) and can cause latency spikes when executed on large data structures. redis.commands.usec tracking per command identifies hot spots.

▸