[SERVER-18760] Track opcounters at a database level Created: 31/May/15  Updated: 01/Jun/15  Resolved: 01/Jun/15

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Joanna Cheng Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-2178 Track stats per db/collection Closed
Participants:

 Description   

Right now we only track opcounters at a instance level. Some customers may want to break this down at a database level to e.g. identify which database(s) are under the most load.

Potential workarounds have been discussed. Tailing the oplog only tracks writes, not reads. To track reads the customer would need to turn on profiling, which can cause issues with performance.



 Comments   
Comment by Ramon Fernandez Marina [ 01/Jun/15 ]

Duplicate of SERVER-2178.

Generated at Thu Feb 08 03:48:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.