...
- Low free main memory less than 25
opReports 3.5.1 and newer include improvements to memory related fields
/path/to/omk/conf/opCommon.json has a new setting withdefault being /opreports/on_invalid_hrcachemem_use_only_hrmem=0.
- With /path/to/omk/conf/opCommon.json set at opreports/opreports/on_invalid_hrcachemem_use_only_hrmem=1,
opReports attempts to detect situations where invalid hrCacheMemUsed and hrCacheMemSize
values are being reported that would cause the memory related fields in the Node Health Report to return as negative values.- In such a case (detect memory related fields in the Node Health Report would negative values),
hrCacheMemUsed and hrCacheMemSize will not be used in the calculation of memory related fields
and a suitable entry to this effect will be logged in opReports.log. - This issue has been detected in docker instances where hrCacheMemUsed and hrCacheMemSize values
were that of the docker host and not that of the docker instance itself.
- In such a case (detect memory related fields in the Node Health Report would negative values),
- With /path/to/omk/conf/opCommon.json set at opreports/opreports/on_invalid_hrcachemem_use_only_hrmem=0:
- In such a case (detect memory related fields in the Node Health Report would negative values),
affected memory related fields will return N/A and a suitable entry to this effect will be logged in opReports.log.
- In such a case (detect memory related fields in the Node Health Report would negative values),
opReports 3.5.1 and newer include an improved percentile function
opReports 3.5.1, and newer ,now use the nearest rank inclusive percentile formula as provided in wikipedia:
https://en.wikipedia.org/wiki/Percentile
...