The free command has multiple options to format the output so that it better matches your requirements. The key figure being the available value as it displays how much memory is still available for running new applications. Memory reserved by the OS to allocate as buffers when process need themĮstimation of how much memory is available for starting new applications, without swapping.Ĭompared to the /proc/meminfo file, the free command provides less information. Unused memory (free= total – used – buff/cache) Memory currently in use by running processes (used= total – free – buff/cache) So I spose to my question.The data represents the used/available memory and the swap memory figures in kilobytes. The free shows both views, including and excluding the cache/buffers.Įssentially I would like to graph/monitor the (MemTotal - (MemFree-Buffers)), or in OID talk, (hrStorageSize.1 - hrStorageDescr.7) HOST-RESOURCES-MIB::hrStorageSize.10 = INTEGER: 12289716 HOST-RESOURCES-MIB::hrStorageSize.8 = INTEGER: 0
HOST-RESOURCES-MIB::hrStorageSize.7 = INTEGER: 2750756 HOST-RESOURCES-MIB::hrStorageSize.6 = INTEGER: 324052 HOST-RESOURCES-MIB::hrStorageSize.3 = INTEGER: 16285348 HOST-RESOURCES-MIB::hrStorageSize.1 = INTEGER: 3995632 HOST-RESOURCES-MIB::hrStorageDescr.10 = STRING: Swap space HOST-RESOURCES-MIB::hrStorageDescr.8 = STRING: Shared memory HOST-RESOURCES-MIB::hrStorageDescr.7 = STRING: Cached memory HOST-RESOURCES-MIB::hrStorageDescr.6 = STRING: Memory buffers HOST-RESOURCES-MIB::hrStorageDescr.3 = STRING: Virtual memory HOST-RESOURCES-MIB::hrStorageDescr.1 = STRING: Physical memory The thing is I want to know/alert if real memory usage gets above say 80%, etc. This isn't a problem in so far as actual memory usage = MemTotal - Cached, however it basically renders default memory monitoring on NPM useless. Its the same story for all recent Linux kernels. The issue is on all our Linux boxes that over time, Physical memory usage always climbs to 99% See attachment. The cache is typically a filesystem cache where the kernel helpfully places recently read/written files for quick retrieval later. The problem is with the "Physical memory" monitoring. Running Net-SNMP 5.4.1 on a wide range of Solaris and Linux boxes /w NPM 9.1 SP5 monitoring a range of params.
0 kommentar(er)
