[DOCS-13665] [OM] COMPUTED_MEMORY dosen't exist through Ops Manager API Created: 26/May/20  Updated: 13/Sep/20  Resolved: 13/Sep/20

Status: Closed
Project: Documentation
Component/s: API, Ops Manager
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Andualem Gurmu Assignee: Anthony Sansone (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

https://docs.opsmanager.mongodb.com/v4.0/reference/api/measures/measurement-types/


Attachments: PNG File screenshot-1.png    
Participants:
Days since reply: 3 years, 21 weeks, 4 days ago
Epic Link: DOCSP-7540
Story Points: 2

 Description   

Description

The documentation states COMPUTED_MEMORY measurement. It doesn't exist when read through Ops Manager, however. Any way we could get total physical memory or total Wired Tiger cache through Ops Manager API?

https://docs.opsmanager.mongodb.com/v4.0/reference/api/measures/measurement-types/



 Comments   
Comment by Anthony Sansone (Inactive) [ 13/Sep/20 ]

I believe development has answered the question. The documentation will be updated with specifics of all values at a later date.

Comment by Anton Oyung [ 24/Jun/20 ]

Answer to OP's first question: 

  • From my findings here, computed memory is described as non-mapped virtual memory, which can be calculated as such 
       COMPUTED_MEMORY = mem-virtual-gauge-mbytes - ( mem-mapped-gauge-mbytes * 2 ) (when journaling is enabled) 
       COMPUTED_MEMORY = mem-virtual-gauge-mbytes - ( mem-mapped-gauge-mbytes ) (when journaling is disabled) 

To answer your questions: 

  • MongoDB
            - Virtual: MEMORY_VIRTUAL found here
            - Physical: MEMORY_RESIDENT 
            - From what I can tell, we don't have a total memory value
  • Wired Tiger
            - I don't think we have any values relating to virtual or physical used bytes for the cache, but we do have CACHE_USED_BYTES 

Let me know if you have further questions! 

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