We should add observability for the replication lag in PCR (current time - replicated time, where the src and dst cluster are exactly the same). Since replication lag is essentially the RPO for customers, we should surface this metric.
P0: calculate replication lag and show in the replication status table (system tenant calls SHOW VIRTUAL CLUSTER .... WITH REPLICATION STATUS)
P1: include graph of replication lag in the DB console so users can see replication lag over time
We should add observability for the replication lag in PCR (current time - replicated time, where the src and dst cluster are exactly the same). Since replication lag is essentially the RPO for customers, we should surface this metric.
P0: calculate replication lag and show in the replication status table (system tenant calls
SHOW VIRTUAL CLUSTER .... WITH REPLICATION STATUS
) P1: include graph of replication lag in the DB console so users can see replication lag over timeJira issue: CRDB-36680