[SERVER-12172] Add finer granularity metrics for serverStatus Created: 19/Dec/13  Updated: 19/Dec/13  Resolved: 19/Dec/13

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: 2.4.8, 2.5.4
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Alvin Richards (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: counters, metrics, stats
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-7382 Track counters for each command Closed
Related
related to SERVER-2178 Track stats per db/collection Closed
related to SERVER-5828 Metric/Stats Tracking Closed
related to SERVER-5980 Track lock queue and active stats per... Closed
Participants:

 Description   

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.



 Comments   
Comment by Scott Hernandez (Inactive) [ 19/Dec/13 ]

All of this is covered in other (linked) issues.

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