Technologies/Redis/redis.keys.evicted
RedisRedisMetric

redis.keys.evicted

Total number of evicted keys due to maxmemory limit
Dimensions:None
Available on:OpenTelemetryOpenTelemetry (1)DatadogDatadog (1)Native (1)PrometheusPrometheus (1)

Summary

Cumulative counter of keys evicted from memory due to maxmemory limit enforcement with an eviction policy (e.g., allkeys-lru, volatile-lru). Non-zero or increasing values indicate memory pressure — Redis is removing keys to make space for new data. High eviction rates degrade cache hit ratios and application performance as frequently accessed data gets evicted. This metric is critical for right-sizing Redis memory allocation and tuning eviction policies.

Interface Metrics (4)
OpenTelemetryOpenTelemetry
Total number of evicted keys due to maxmemory limit
Dimensions:None
DatadogDatadog
Keys evicted due to maxmemory
Dimensions:None
Native
Number of evicted keys due to maxmemory limit
Dimensions:None
PrometheusPrometheus
Keys evicted due to maxmemory
Dimensions:None
Related Insights (2)
Memory Fragmentation Amplifies Cache Eviction Pressurewarning

High Redis memory fragmentation ratio (>1.5) causes actual memory usage to exceed redis.memory.maxmemory limits, triggering premature key evictions and reducing cache hit rates even when logical memory usage appears healthy.

High Eviction Rate Indicates Memory Pressurewarning

When redis.keys.evicted rate increases significantly, Redis is evicting keys to stay within maxmemory limits, potentially causing cache miss storms and degraded application performance as hot data is prematurely evicted.