[DOCS-1186] Question regarding data collection for mongoDB lock % Created: 01/Mar/13  Updated: 01/Mar/13  Resolved: 01/Mar/13

Status: Closed
Project: Documentation
Component/s: Cloud Manager
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Robert Lai Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

--mongo*.i.kixeye.com


Attachments: File lock%.rtf    
Issue Links:
Duplicate
duplicates DOCS-933 MMS - need a brief blurb plus link to... Closed
Participants:
Days since reply: 10 years, 50 weeks, 5 days ago

 Description   

We would like to know how the mms interface is collecting data for calculation of the "lock %" metric. We are seeing discrepancies in our own graphing in which we are seeing data differences between our lock % graphs and the MMS lock % graphs.

I have attached a file containing the method for collection we are currently using. It was pulled from a python script. Can you please document the data collection method/algorithm being employed by the MMS GUI for the lock % metric so we can compare? Or might you have some insights into why our collection method may display different data than the MMS GUI?

Thank you.



 Comments   
Comment by Sam Kleinman (Inactive) [ 01/Mar/13 ]

We'll get this into the documentation soon, but the lock% chart catches the global lock % plus the lock% on the most locked database. I'm going to close this ticket as a duplicate of DOCS-933.

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