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

pve_memory_free_bytes is required #300

Open
sTiKyt opened this issue Dec 2, 2024 · 1 comment
Open

pve_memory_free_bytes is required #300

sTiKyt opened this issue Dec 2, 2024 · 1 comment

Comments

@sTiKyt
Copy link

sTiKyt commented Dec 2, 2024

pve_memory_available_bytes is required because pve_memory_size_bytes shows the total memory size, and pve_memory_usage_bytes shows ALL used bytes, even the ones that are cached (which is a normal linux behavior), so this metric becomes useless for monitoring of free memory available

In pve_memory_available_bytes, I'd expect to see this:
image

As you can see it's only reporting 334M as free Memory, which is triggering all the alerts i have, because it thinkns all my RAM is used (while in reality 18G out of 31 are cached and will automatically release if some parts of the system require it)

@znerol
Copy link
Member

znerol commented Dec 2, 2024

Metrics for nodes, VMs and containers are gathered via the PVE API. See the docs for all the values which are available.

You can also check what is available from the API with the pvesh command line tool.

Thus, if you find the value in the API, then we can maybe add it as a metric. Also I'd recommend to try node_exporter to scrape platform specific metrics.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants