Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

[stable/prometheus-operator] node_filesystem_*_bytes on /var/lib/docker partition with / device #22905

Closed
wu105 opened this issue Jun 22, 2020 · 3 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@wu105
Copy link

wu105 commented Jun 22, 2020

Describe the bug
The node_filesystem_..._bytes (... is size, free, available) metrics reported by node-exporter are on the node partition /var/lib/docker and is always reported with mountpoint as / and the device of the / partition. The mountpoint is debatable but the device would be wrong if /var/lib/docker has its own partition. See prometheus/node_exporter#1754 for more details.

Version of Helm and Kubernetes:
Irrelevant.

Which chart:
stable/prometheus-operator-5.5.1

What happened:
See description above.

What you expected to happen:
We would like to see the device reported correctly out of box.
Node exporter has its share of the problem and may help to improve the overall situation.
It may help with documentation and support for configuring node exporter on host partitions to be monitored and explain the metrics collected.

How to reproduce it (as minimally and precisely as possible):
Deploy prometheus on a cluster with some nodes have /var/lib/docker on a non-root partition and check the node_filesystem_..._bytes metrics' device label.

Anything else we need to know:

@tuxknight
Copy link
Contributor

default value in this chart didn't mount rootfs to node-exporter, you could add this to values.yaml

extraArgs:
  - "--path.rootfs=/host/root"

extraHostVolumeMounts:
  - name: root
    hostPath: /
    mountPath: /host/root
    readOnly: true
    mountPropagation: HostToContainer

@stale
Copy link

stale bot commented Aug 22, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 22, 2020
@stale
Copy link

stale bot commented Sep 5, 2020

This issue is being automatically closed due to inactivity.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants