The sharding section in serverStatus currently reports lastSeenConfigServerOpTime (aka configOpTime). However, this field is being replaced by the VectorClock's ConfigTime component. Probably the current VectorClock time (currently ClusterTime, ConfigTime, and TopologyTime) should be reported somewhere in serverStatus. The clusterTime is currently not reported anywhere in serverStatus. We should choose an appropriate place to put these values, including appropriate interactions with FTDC. For example, since clusterTime (and to a lesser degree ConfigTime) increments frequently, it may not be efficient to fetch in a periodic collector in FTDC (but an onRotate collector should be okay). It should also be determined if this info should be ordinarily visible in serverStatus, or in a (possibly new) default-hidden section.