-
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
Feature: Alllow filtering out some filesystem types #3459
Labels
enhancement
help wanted
Indicates that a maintainer wants help on an issue or pull request
Metricbeat
Metricbeat
Comments
Does that work well enough for you? |
That's great! |
cv
added a commit
to cv/beats
that referenced
this issue
Jul 31, 2017
Its value is copied from sigar.FileSystem.SysTypeName (on Windows, sigar.FileSystem.TypeName) and passed through so that it becomes possible to filter out `overlay`, `tmpfs` or otherwise uninteresting filesystems. Fixes elastic#3459.
andrewkroh
pushed a commit
that referenced
this issue
Aug 2, 2017
tsg
pushed a commit
to tsg/beats
that referenced
this issue
Aug 24, 2017
Its value is copied from sigar.FileSystem.SysTypeName (on Windows, sigar.FileSystem.TypeName) and passed through so that it becomes possible to filter out `overlay`, `tmpfs` or otherwise uninteresting filesystems. Fixes elastic#3459. (cherry picked from commit 94a197b)
andrewkroh
pushed a commit
that referenced
this issue
Aug 24, 2017
…4991) * Adds a "type" field to the filesystem beat (#4717) (#4717) Its value is copied from sigar.FileSystem.SysTypeName (on Windows, sigar.FileSystem.TypeName) and passed through so that it becomes possible to filter out `overlay`, `tmpfs` or otherwise uninteresting filesystems. Fixes #3459. (cherry picked from commit 94a197b)
leweafan
pushed a commit
to leweafan/beats
that referenced
this issue
Apr 28, 2023
…m beat (elastic#4991) * Adds a "type" field to the filesystem beat (elastic#4717) (elastic#4717) Its value is copied from sigar.FileSystem.SysTypeName (on Windows, sigar.FileSystem.TypeName) and passed through so that it becomes possible to filter out `overlay`, `tmpfs` or otherwise uninteresting filesystems. Fixes elastic#3459. (cherry picked from commit 7e2396a)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
help wanted
Indicates that a maintainer wants help on an issue or pull request
Metricbeat
Metricbeat
Feature Request
Original Thread:
https://discuss.elastic.co/t/disk-space-metrics-wrong-when-working-with-overlay-mounts/72442
There is currently a problem when using overlay mounts. In such case, the mount point has the same disk size as the original disk. In Kibana, these sizes are summed what is not the reality.
It should be possible, to allow filtering out all such types to only transmit the real size of the disk.
The text was updated successfully, but these errors were encountered: