Open
Description
Currently, a PCR user has no visibility into the historical time that the reader tenant uses to query the app tenant. In the happy case, it's approximately equal to the replicated time, but it can fall behind if the reader tenant job poller job stalls for some reason.
As a very first step, we should update the standby poller job's resolved time in the system.job_progress table so a user logged into the reader tenant's db console can observe it.
However, we should strive to simplify the PCR UX such that all PCR observability can be viewed from the system tenant, via SHOW TENANT WITH REPLICATION STATUS and system tenant time series metrics.
Jira issue: CRDB-51634