Currently, there lacks visibility into the time a user-initiated command like find or update spends in different parts of the system and between mongos and mongod after being sent from the driver. To debug help tickets or identify performance bottlenecks in a command, a user may want to know the time spent by a query in index scans, disk access etc. It would be great if such a capability could be added to the commands in a way such that any new command implemented can use this instrumentation library to opt into instrumenting different parts of its execution lifecycle and the instrumentation metrics for existing commands can be fetched on turning instrumentation on.