Technologies/Redis/redis.db.expires
RedisRedisMetric

redis.db.expires

Number of keys with an expiration
Dimensions:None
Available on:DatadogDatadog (1)Native (1)OpenTelemetryOpenTelemetry (1)

Summary

Current number of keys in a specific database that have an expiration time set. Monitoring this metric helps ensure that cache entries and temporary data have proper lifecycle management. A decreasing ratio of expiring keys to total keys may indicate applications are not setting TTLs, leading to unbounded memory growth. Cross-reference with eviction metrics to detect scenarios where keys without TTLs force eviction of valuable cached data.

Interface Metrics (3)
DatadogDatadog
Keys with an expiration
Dimensions:None
Native
Number of keys with an expiration in the database
Dimensions:None
OpenTelemetryOpenTelemetry
Number of keys with an expiration
Dimensions:None
Sources
redis.expiresdocs.datadoghq.com
redis.keyspace.expiresredis.io
redis.db.expiresopentelemetry.io
Related Insights (1)
Expiring Keys Without TTL Monitoring Causes Memory Leakswarning

When redis.persist count is high relative to redis.db.expires, many keys lack TTLs and will accumulate indefinitely, causing memory growth. redis.keyspace.avg_ttl can indicate if TTL values are too long for workload patterns.

▸