Skip to content

Fix filesystem collector filters: overlay fstype and containerd mount paths - #360

Open
alvinnguyen0 wants to merge 1 commit into
digitalocean:masterfrom
alvinnguyen0:an/fix-filters
Open

Fix filesystem collector filters: overlay fstype and containerd mount paths#360
alvinnguyen0 wants to merge 1 commit into
digitalocean:masterfrom
alvinnguyen0:an/fix-filters

Conversation

@alvinnguyen0

Copy link
Copy Markdown

Summary

The filesystem collector's exclude filters have gaps that let container runtime
mounts through. This inflates series count on and added noise to the Droplet Insights Disk Usage chart.

  • overlayfs doesn't show up in mount tables, but overlay does, and was seen in Insights disk usage charts. Changing this to overlay will also match overlayfs.

  • containerd added alongside docker in ignoredMountPoints as precaution to catch any containerd mounts whose type isn't overlay.

  • Verified that the Droplet Insights disk chart groups no longer shows extraneous mounts by deploying a prerelease image on a live Kubernetes node and confirmed the excess mounts are gone from Insights chart on the Droplet.

@alvinnguyen0
alvinnguyen0 requested a review from a team as a code owner September 2, 2026 00:29

@m3co-code m3co-code left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but needs another approval from someone from the insights team I think.

@alvinnguyen0 alvinnguyen0 changed the title Fix filesystem collector filters: overlay fstype and containerd/kubelet mount paths Fix filesystem collector filters: overlay fstype and containerd mount paths Sep 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants