-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
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
[Metricbeat] Excluding bind mounts #3384
Comments
The fsstat module is really useless atm, please exclude mount points and subpaths by default. |
Mountpoints whose device name is the same absolute path are considered to be the same and are counted only once. The directory name used is the shorter between them. This avoids duplication of filesystems as can happen with bind mounts in Linux (elastic#3384).
* Metricbeat: Remove duplicated filesystems in system module Mountpoints whose device name is the same absolute path are considered to be the same and are counted only once. The directory name used is the shorter between them. This avoids duplication of filesystems as can happen with bind mounts in Linux (#3384). * Metricbeat: Ignore nodev filesystems by default In system module, when no filesystem type is set to be ignored, it tries to make a sane guess. In systems with /proc/filesystems file it ignores all devices marked as `nodev`.
After #6819, each filesystem should appear only once even if it is mounted multiple times, if it is, only the shorter mount path is reported. Bind mounts won't be reported as it is assumed that the source/parent filesystem is also mounted and reported on its own. Also, file systems of "virtual" filesystem types won't be reported by default (these types are autodiscovered when possible and added to I hope this helps to make these metricsets more useful by default, closing this by now. |
Sounds great, thanks! In which version will this be included? |
@abraxxa 6.3 |
Feature request per https://discuss.elastic.co/t/excluding-bind-mounts/71509
install and configure metricbeat to collect filesystem/fsstat data
look at both installed Kibana dashboards, storage space is counted multiple times when bind mounts exist
Suggested solution:
Add a filesystem type field to the mapping, add a filter to the default config or hardcode exclude bind mounts (that would always make sense for fsstat as the total space is wrong with them).
The text was updated successfully, but these errors were encountered: