When running db._adminCommand('top') it seems that the values that get sent back are effected by the command. Meaning, I could have 10 queries on a particular collection before running the top command, however after running the top command it jumps up a large amount (have not tested for the exact amount) to something like 120 queries.

I spoke with Kyle regarding this and he asked me to open an issue since it may be a bug. We are trying to figure out what and how many times a collection is 'touched' when top is run on the server.