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
collectd:df plugin assumes that /etc/mtab is populated accordingly to the collectd logs inside the k8ssadra managed deployment which breaks the disk stats exporter as no mounts are detected
[2022-03-24 01:05:59] setmntent (/etc/mtab): No such file or directory
[2022-03-24 01:05:59] df plugin: cu_mount_getlist failed.
Does this makes sense to update the Dockerfile and add a symlink /etc/mtab -> /proc/mounts so C* disks can be monitored?
┆Issue is synchronized with this Jira Task by Unito
┆friendlyId: K8SSAND-1361
┆priority: Medium
The text was updated successfully, but these errors were encountered:
sync-by-unitobot
changed the title
add /etc/mtab to /proc/mounts symlink to account for the containerd runtime collectd disk monitor
K8SSAND-1361 ⁃ add /etc/mtab to /proc/mounts symlink to account for the containerd runtime collectd disk monitor
Mar 29, 2022
Hi,
There is a change when it comes to using the containerd compare to moby runtime as containerd does not create the default symlinks
collectd:df plugin assumes that /etc/mtab is populated accordingly to the collectd logs inside the k8ssadra managed deployment which breaks the disk stats exporter as no mounts are detected
Does this makes sense to update the Dockerfile and add a symlink
/etc/mtab -> /proc/mounts
so C* disks can be monitored?┆Issue is synchronized with this Jira Task by Unito
┆friendlyId: K8SSAND-1361
┆priority: Medium
The text was updated successfully, but these errors were encountered: