Technologies/Redis/redis.persistence.aof_last_rewrite_time_sec
RedisRedisMetric

redis.persistence.aof_last_rewrite_time_sec

Duration of last AOF rewrite
Dimensions:None
Available on:DatadogDatadog (1)Native (1)PrometheusPrometheus (1)

Summary

Duration in seconds of the most recent AOF rewrite operation. AOF rewrites compact the append-only file by replaying operations to generate a minimal snapshot. Long rewrite times (>60s) indicate large datasets, slow disk I/O, or CPU constraints. Extended rewrites can impact performance as Redis maintains both old and new AOF files during the operation, and can trigger latency spikes mentioned in the AOF persistence latency insight.

Interface Metrics (3)
DatadogDatadog
Duration of last AOF rewrite
Dimensions:None
Native
Duration of the last AOF rewrite operation
Dimensions:None
PrometheusPrometheus
Duration of last AOF rewrite
Dimensions:None
Sources
redis.aof.last_rewrite_timedocs.datadoghq.com
redis.persistence.aof_last_rewrite_time_secredis.io
redis_aof_last_rewrite_duration_secgithub.com
Related Insights (1)
AOF Persistence Latency from Synchronous Disk Writeswarning

When AOF persistence is enabled with appendfsync always or everysec, slow disk I/O can cause write latency spikes. redis.persistence.aof_last_rewrite_time_sec increasing significantly indicates AOF file growth without rewrite, amplifying disk I/O overhead.

▸