$ mongo --port 29913 --eval 'db.getSiblingDB("test").ts.stats().timeseries' > ts_execstats

$ cut -d'"' -f2 ./ts_execstats | tail -n +6 | head -n 31 | xargs -I% sh -c "echo \"${CYAN}%${ENDCOLOR}\" && grep -rH --color=always \"assert.eq([1-9].*%\" jstests/noPassthrough/timeseries" 

If these metrics mean anything, the second command above should yield a result for every stat. So far these are missing (generally, they only check equivalence to 0). This ticket is to ensure that each metric is tested to move successfully.

After filtering out metrics checked in jstests/noPassthrough/timeseries/timeseries_collStats.js, here's the final list of untested metrics:

• numBucketsClosedDueToSchemaChange
• numBucketsClosedDueToTimeBackward

• numBucketsClosedDueToMemoryThreshold (unclear, perhaps a stronger check in timeseries_side_bucket_catalog_memory_usage_threshold.js)

• numMeasurementsGroupCommitted

• numWaits

• numBucketsClosedDueToReopening

• numBucketsFetched

• numBucketsQueried

• numBucketFetchesFailed

• numDuplicateBucketsReopened