Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Free/Used-Confusion #9

Open
UweOhse opened this issue Apr 28, 2019 · 2 comments
Open

Free/Used-Confusion #9

UweOhse opened this issue Apr 28, 2019 · 2 comments
Labels
bug Something isn't working

Comments

@UweOhse
Copy link

UweOhse commented Apr 28, 2019

Hello,

the "free" values of ram, swap, disk in the output of pve_exporter are really the "used" values from the PVE node.
I think this should be fixed.

Shall i just rename them, or add "used"-values and fix the "free" values, or add "used" and leave "free" alone for some grace period?

Regards, Uwe

@wakeful
Copy link
Owner

wakeful commented Apr 30, 2019

thanks for reporting this - can you share your pve version?
I would say create / add "used" and keep the "free" for now.

@wakeful wakeful added the bug Something isn't working label Apr 30, 2019
@mozai
Copy link

mozai commented Jun 1, 2020

We're using PVE v6.1. I ran into this myself. Does not help that the "mem" metric appears to be undocumented.

pvesh get /nodes/${name}/lxc --output-format json reports
"[{"maxmem": 36507222016, "mem": 571985920,}] or 1.6% .

Looking from inside the LXC with
cat /proc/meminfo |perl -ne '/MemFree:\s*(\d+)/ and $f=$1; /MemAvailable:\s*(\d+)/ and $a=$1; /MemTotal:\s*(\d+)/ and $t=$1; END{ printf("Avail %.3f\nFree: %.3f\n",($a/$t),($f/$t)); }'
I get 98.4 available, the inverse of 1.6%. This leads me to believe the "mem" metric reported by PVE is "memory in-use" not "memfree".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants