Problem:
db.serverStatus() provides a high level aggregate of command, inserts, updates etc. that occur on a system. This information is transient (ie. reset when the mongod re-starts) but provide a valuable insight on the running system.
However, the aggregation looses the details of where the operations are occuring, for example that the reads are to Collection X in DB Y, the updates are happening to Collection A on DB B etc.
Request:
Provide lower level metrics down to the collection level, for example
system
+ commands
-- eval, fsync, getlasterror
+- database
-- authenticate
+- collection
+ command
-- map reduce, count, distinct, aggregate, move chunk, drop, ensureindex, compact, findandmodify, geoXXX, group, splitchunk, splitvector
+ insert, query, getmore, update, remove
Rationale:
Getting better insight into the running system will help to diagnose issues more accurately.
- duplicates
-
SERVER-7382 Track counters for each command
-
- Closed
-
- related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-