You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ts=2022-08-08T15:09:42.577Z caller=filesystem_common.go:111 level=info collector=filesystem msg="Parsed flag --collector.filesystem.mount-points-exclude" flag=^/(dev|proc|run/credentials/.+|sys|var/lib/docker/.+)($|/)
ts=2022-08-08T15:09:42.577Z caller=filesystem_common.go:113 level=info collector=filesystem msg="Parsed flag --collector.filesystem.fs-types-exclude" flag=^(autofs|binfmt_misc|bpf|cgroup2?|configfs|debugfs|devpts|devtmpfs|fusectl|hugetlbfs|iso9660|mqueue|nsfs|overlay|proc|procfs|pstore|rpc_pipefs|securityfs|selinuxfs|squashfs|sysfs|tracefs)$
the mounts within the pod show up with the /host/root prefix, so I suspect the regular expression isn't matching.
shm on /host/root/run/containerd/io.containerd.grpc.v1.cri/sandboxes/b7fc03b87b11f94e3ec41a04a9ef91f3159d37382369391b2e4159529c58808d/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
It would be nice if the path.rootfs prefix was taken into account by the filesystem excluding code, so users wouldn't have to
The text was updated successfully, but these errors were encountered:
My apologies, I've actually just noticed that the default regular expression is for run/credentials/.+ which doesn't exclude these mountpoints, which are run/containerd...
For the record, if I tweak the the regular expression to be run.*, it works fine with the path.rootfs, and also works with path.procfs and path.sysfs in there at the same time. So this is entirely just me misreading the regular expression - sorry about that.
For what it's worth, I suspect that excluding everything in the run directory would probably be a good default, this regexp works for that:
or, perhaps more contentiously, adding tmpfs to fs-types-exclude is another solution.
But obviously I can just fix this with a local config change.
I'm running node exporter within Kubernetes 1.22 on Ubuntu 20.04, installed with kubeadm, which should be a fairly common installation for people, so I expect this to show up more in future. Alternatively, I could suggest that the node exporter helm chart adds these configs locally, if you don't think they belong here.
version=1.3.1, branch=HEAD, revision=a2321e7b940ddcff26873612bccdf7cd4c42b6b6
I'm running node_exporter within kubernetes, using the community helm chart. It sets up the current mounts:
metrics are being reported for filesystems mounted within the /run directory, despite being excluded by the default config, e.g:
the mounts within the pod show up with the /host/root prefix, so I suspect the regular expression isn't matching.
It would be nice if the path.rootfs prefix was taken into account by the filesystem excluding code, so users wouldn't have to
The text was updated successfully, but these errors were encountered: