Technologies/Redis/redis.replication.offset
RedisRedisMetric

redis.replication.offset

The server's current replication offset
Dimensions:None
Available on:Native (1)DatadogDatadog (1)PrometheusPrometheus (1)OpenTelemetryOpenTelemetry (1)

Summary

Current position in the replication stream, representing how much data has been processed. On masters, this is the write position; on replicas, it's the replay position. The delta between master and replica offsets is the replication lag in bytes. Growing deltas indicate replicas falling behind, which can lead to the scenario described in the insight about replica lag hiding behind stale cache hits.

Interface Metrics (4)
Native
The server's current replication offset
Dimensions:None
DatadogDatadog
Server's current replication offset
Dimensions:None
PrometheusPrometheus
Server's current replication offset
Dimensions:None
OpenTelemetryOpenTelemetry
Server's current replication offset
Dimensions:None
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.