maybe you know the issue: having a fixed warning and critical threshold in check_disk is quite problematic, because it is depending on the disk‘s size. 10% free or 10GB free makes a great difference if your disk is 100GB or 10TB.
Maintaining the thresholds manually for each service is unhandy as well.
Apply rules are not working or you have to maintain the disk size in custom vars again…so…then I could maintain the threshold as well…
How are you dealing with this?
Is there anything nice like dynamic thresholds? I stumbled over such an approach at another monitoring solution. There the threshold can be adjusted by a magic factor (e.g. 0.8) which is related to a base size (e.g. 100GB). At exactly 100GB disk size you would have 1.0 threshold (no change). At lower disk size you would have a decreased threshold at higher ones an increased.