Performance issues can occur when there are high quantities of MVCC garbage data. MVCC garbage data can lead to downstream issues like resource saturation that we’ve seen in several customer workloads (e.g., the outbox pattern).

We should surface MVCC garbage information specifically in SQL Observability touchpoints such as our internal telemetry, aggregated statement and transaction statistics tables, and the console (SQL Activity pages and Insights).

This issue tracks surfacing MVCC garbage information in our aggregated statement and transaction statistics tables and console pages. We should strive for a simple and explainable metric and UX that points users to MVCC garbage accumulation. Ideally the UX should be consistent with MVCC values surfaced in the Databases page where we describe "Live" and "Non-Live" data. Specifically, we should introduce liveBytesRead and nonLiveBytesRead per execution.

Related issues:

• sql: add MVCC steps and seeks to EXPLAIN ANALYZE #64503 added MVCC step/seek information to EXPLAIN(ANALYZE). Since we're collecting this information now, we should be able to at least sample it and include it in our statistics.

cc @maryliag @kevin-v-ngo @dongniwang

Jira issue: CRDB-10925

Jira issue: CRDB-13485

Epic: CRDB-20499