Details
-
Task
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
None
Description
Mongod captures the latency metrics of reads and writes to a collection and exposes them via $collStats. However, mongos doesn't do that. Running $collStats against a mongos returns the latencyStats for each shard in a separate document along with the other stats. Similar to SERVER-46478, we should make mongos capture per-collection latency metrics to allow for performance analysis after (re)sharding and other cases.
Attachments
Issue Links
- is related to
-
SERVER-46478 Add opLatencies to mongoS serverStatus
-
- Closed
-