-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
node_memory_MemAvailable_bytes is missing when node_memory_MemTotal is avaliable #1689
Comments
Not sure what you're talking about. node_memory_MemTotal_bytes and node_memory_MemAvailable_bytes are the metric name. There is no metric node_memory_MemTotal. Does that clarify this? |
You can view the two pictures I provided, these two pictures are different nodes, but one can find one and cannot find. This two nodes spec is same. |
Just to confirm -- both use the exact same kernel version / Linux distribution release, right? |
Sorry late to reply, I have check some cannot find node_memory_MemAvailable_bytes node. Is different service provider nodes. Maybe is CentOS 6.10 promblem。 |
Ok, looks like you need a newer kernel for this. We can't do anything about that, so closing this. |
Host operating system: output of
uname -a
Linux ip-172-31-39-30.ap-east-1.compute.internal 3.10.0-1062.4.3.el7.x86_64 #1 SMP Wed Nov 13 23:58:53 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
node_exporter version: output of
node_exporter --version
node_exporter, version 0.18.1 (branch: HEAD, revision: 3db7773)
build user: root@b50852a1acba
build date: 20190604-16:41:18
go version: go1.12.5
node_exporter command line flags
/usr/local/greycdn/node_exporter/node_exporter --web.listen-address=:6192 --web.telemetry-path=/node_info
Are you running node_exporter in Docker?
No
What did you do that produced an error?
By filtering data in Prometheus.
What did you expect to see?
Can found node_memory_MemAvailable_bytes
What did you see instead?
node_memory_MemAvailable_bytes can found
Note:
I have try reinstall node_exporter but issue still abailable.
The text was updated successfully, but these errors were encountered: