Extend the "Filesystem discover" rule with more filesystems or/and add regex filters
Extend the "Filesystem discover" rule to exclude more filesystems like Overlay Filesystems from Kubernetes Nodes or allow adding regex filters.
In our Kubernetes environment, in which we use Longhorn for storage, each node has several overlay file systems, but they all only display the fill level of the second hard disk of the server and are therefore redundant.
Currently, these services are simply deactivated. It would be nicer not to have them discovered at all if they are not needed.
Comments: 3
-
16 Jun, '22
Cameron MooreWe monitor a few QNAP storage appliances that have snapshot volumes that come and go, which causes Filesystem services to disappear and reappear. We want the ability to do the opposite of the "Mountpoints to never ignore" settings. We would ignore all "[/]mnt[/]snapshot[/].*" mountpoints.
-
16 Feb, '23
Sven Rubenfor my opinion, you can already do that in the ruleset „Service discovery rules“ with the „Disabled services“ rule …
- Conditions
- Services
- „Filesystem C:/Users/“
that one works for me for RDS UserProfileDisks that are mapped there … so would work for linux too with „Filesystem /mnt/snapshot/“ for your example (remember: no $ and the end means everything that start with the string) -
18 Oct, '23
Martin Hirschvogel AdminFor Kubernetes monitoring, we have a different method via the Kubernetes Collectors which now also include the ability to monitor filesystems as you desire since a couple of weeks. This solves your underlying wish.