It was observed during some investigations that table level metrics for shippedBytes are always 0 consistently even though data is getting shipped.
There are two problems with table-level metrics:
- There are no table-level metrics for shipped bytes.
- Another problem is that it's using `MetricsReplicationSourceSourceImpl` which is creating all source-level metrics at table level as well but updated only ageOfLastShippedOp. This reports lot of false/incorrect replication metrics at table level.