-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Admin, Internal Code
-
Minor Change
-
Server 2.7.4, Server 2.7.5, Server 2.7.6
For each command we should track a counter, like opcounters in serverStatus and a gauge for the active/waiting operations by command type.
This will provide a counter for each command showing the number of times it has been executed and the number of times that the execution has failed. It will also track the number of times any unknown/invalid command is executed.
This will track writes that are issued via the write command syntax. Due to this the values between the already existing command counter and the new counters may be off.
Example shell usage:
> db.serverStatus().metrics.commands { "<UNKNOWN>" : NumberLong(0), "_getUserCacheGeneration" : { "failed" : NumberLong(0), "total" : NumberLong(0) }, "_isSelf" : { "failed" : NumberLong(0), "total" : NumberLong(0) }, "_mergeAuthzCollections" : { "failed" : NumberLong(0), "total" : NumberLong(0) }, "_migrateClone" : { "failed" : NumberLong(0), "total" : NumberLong(0) }, "_recvChunkAbort" : { "failed" : NumberLong(0), "total" : NumberLong(0) }, ... }
- is duplicated by
-
SERVER-12323 findAndModify not counted properly in opcounters
- Closed
-
SERVER-12172 Add finer granularity metrics for serverStatus
- Closed
- is related to
-
SERVER-5787 Track opcounters (insert/delete/update) which results from sharding commands
- Closed
- related to
-
SERVER-5828 Metric/Stats Tracking
- Closed
-
SERVER-15870 suppress uncalled commands from db.serverStatus() in the shell
- Closed
- links to