Node_exporter: node_memory_MemAvailable_bytes is missing when node_memory_MemTotal is avaliable

[wiljay]

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: 3db77732e925c08f675d7404a8c46466b2ece83e)
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.

[discordianfish]

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?

[wiljay]

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.

[hoffie]

This two nodes spec is same.

Just to confirm -- both use the exact same kernel version / Linux distribution release, right?
I'm asking because older kernels to not expose MemAvailable (especially RHEL6; RHEL7 -- your kernel looks like that -- does).

[wiljay]

This two nodes spec is same.

Just to confirm -- both use the exact same kernel version / Linux distribution release, right?
I'm asking because older kernels to not expose MemAvailable (especially RHEL6; RHEL7 -- your kernel looks like that -- does).

Sorry late to reply,

I have check some cannot find node_memory_MemAvailable_bytes node. Is different service provider nodes.
alicloud
CentOS release 6.10 (Final)
Linux iZj6cac6ryn1mjk0nterqmZ 2.6.32-696.16.1.el6.x86_64 #1 SMP Wed Nov 15 16:51:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
CentOS release 6.10 (Final)
Linux iZj6cbfvkmy1wcrs480knyZ 2.6.32-696.16.1.el6.x86_64 #1 SMP Wed Nov 15 16:51:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
tencent
CentOS release 6.10 (Final)
Linux VM_0_14_centos 2.6.32-696.el6.x86_64 #1 SMP Tue Mar 21 19:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
azure
CentOS release 6.10 (Final)
Linux greycdn031 2.6.32-754.17.1.el6.x86_64 #1 SMP Tue Jul 2 12:42:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Maybe is CentOS 6.10 promblem。

[discordianfish]

Ok, looks like you need a newer kernel for this. We can't do anything about that, so closing this.