We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, when monitoring container disks with cadvisor v0.49.1 on a docker host with
v0.49.1
"storage-driver": "overlay2"
the metric container_fs_inodes_free shows 0 constantly.
container_fs_inodes_free
0
From what I have gathered from the code it should count the number of files to calculate this metric, but this does not seem be the case.
Can anybody confirm that this is a supported feature or should I disable disk metrics for this setup?
disk
The text was updated successfully, but these errors were encountered:
Remove alert rule ContainerVolumeUsage
4edb77e
At least with storage-driver `overlay2` the metric `container_fs_inodes_free` shows zero for all containers. See google/cadvisor#3534 Part of osism/issues#1009 Signed-off-by: Jan Horstmann <[email protected]>
No branches or pull requests
Hi,
when monitoring container disks with cadvisor
v0.49.1
on a docker host withthe metric
container_fs_inodes_free
shows0
constantly.From what I have gathered from the code it should count the number of files to calculate this metric, but this does not seem be the case.
Can anybody confirm that this is a supported feature or should I disable
disk
metrics for this setup?The text was updated successfully, but these errors were encountered: