[SERVER-26548] How can one spot 2.6 serverStatus / executionStats / log Output equivalents in 3.2 WiredTiger? Created: 10/Oct/16  Updated: 13/Oct/16  Resolved: 12/Oct/16

Status: Closed
Project: Core Server
Component/s: Diagnostics, Usability, WiredTiger
Affects Version/s: 3.2.10
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Avraham Kalvo Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Having recently upgrading our entire Mongo DB replica sets array to 3.2.10,
We noticed that our monitoring scripts, which used to utilise specific metrics available on 2.6 began breaking due to having these metrics no longer available to them using serverStatus.

Can you please refer us to the equivalent (whether WiredTiger related or not) metric names for the following metrics?

memory accessesNotInMemory
memory pageFaultExceptionsThrown
memory admin accessesNotInMemory
memory admin pageFaultExceptionsThrown
memory local accessesNotInMemory
memory local pageFaultExceptionsThrown
memory test accessesNotInMemory
memory test pageFaultExceptionsThrown
memory wixExpress accessesNotInMemory
memory wixExpress pageFaultExceptionsThrown
flushing flushes
flushing total_ms
flushing average_ms
flushing last_ms
flushing last_finished
indexes accesses
indexes hits
indexes misses
indexes resets
indexes missRatio
journaling commits
journaling journaledMB
journaling writeToDataFilesMB
journaling compression
journaling commitsInWriteLock
journaling earlyCommits
journaling timeMs dt
journaling timeMs prepLogBuffer
journaling timeMs writeToJournal
journaling timeMs writeToDataFiles
journaling timeMs remapPrivateView

plus, we noticed that our 3.2.10 nodes no longer produce the level of detail in terms of queries stats served. i.e, we used to have:

ntoreturn:20 ntoskip:0 nscanned:45644 nscannedObjects:45644 scanAndOrder:1 keyUpdates:0 writeConflicts:0 numYields:1426 nreturned:1 reslen:6790 locks:{ Global: { acquireCount: { r: 2854 } }, Database: { acquireCount: { r: 1427 } }, Collection: { acquireCount: { r: 1427} } } 1845ms

and now cannot find their equivalent on the new logs...
is there some sort of backward compatibility flag to be switched on, or a log level one missing here?

Thanks,
Avi Kalvo
WiX.COM



 Comments   
Comment by Avraham Kalvo [ 13/Oct/16 ]

Many thanks Thomas,
You may close this SR.

Comment by Kelsey Schubert [ 12/Oct/16 ]

Hi avrahamk,

Thanks for your report. Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group.

Kind regards,
Thomas

Generated at Thu Feb 08 04:12:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.