Technologies/Redis/redis.replication.master_last_io_seconds_ago
RedisRedisMetric

redis.replication.master_last_io_seconds_ago

Seconds since last interaction with master
Dimensions:None
Available on:DatadogDatadog (1)Native (1)PrometheusPrometheus (1)

Summary

Seconds since the replica last received any data from its master, including replication stream or pings. Values >10 seconds indicate replication stalling or network issues between master and replica. Extended delays mean the replica is falling behind and may be serving stale data. This is a leading indicator of replication lag issues referenced in the insight about replica lag hiding behind stale cache hits.

Interface Metrics (3)
DatadogDatadog
Seconds since last interaction with master
Dimensions:None
Native
Number of seconds since the last interaction with master
Dimensions:None
PrometheusPrometheus
Seconds since last interaction with master
Dimensions:None
Sources
redis.replication.last_io_seconds_agodocs.datadoghq.com
redis.replication.master_last_io_seconds_agoredis.io
redis_master_last_io_seconds_agogithub.com
Related Insights (1)
Replica Lag Hides Behind Stale Cache Hitscritical

Redis replica falling behind master (redis.replication.master_last_io_seconds_ago increasing) continues serving stale cached data with normal hit rates, masking synchronization issues until applications encounter data inconsistencies or master failover fails.

▸