Hi David,
this looks like a known interaction between the Magic Factor and absolute free space levels in Checkmk 2.2.
Even though your specific rule (position 0) is correctly matched in “Effective Parameters”, the Magic Factor configured in your global rule (position 1) can still interfere — because sub-parameters from multiple rules are merged. When the Magic Factor is active, it can override the absolute levels with its own levels_low fallback values.
Two things to try:
-
In your specific rule (position 0): Explicitly set the Magic Factor to 1.0 (= no scaling) and make sure “Minimum levels if using magic factor” is either disabled or set to non-critical values.
-
In your global rule (position 1): Make sure the Magic Factor checkbox is not applying to the host/mountpoint already covered by your specific rule — or disable it there entirely.
This exact bug (absolute free space levels ignored when Magic Factor = 1.0) was fixed in Werk #15908, released with 2.2.0p8. Since you’re on 2.2.0p47 the fix should be present, so the issue is most likely the sub-parameter merging between your two rules.
References:
- BUG: 2.2 and levels for absolute free space & magic factor not working together
- Werk #15908: df: Showing wrong WARN/CRIT levels when magic factor is 1.0
- https://checkmk.com/werk/14318
try it out …
Bernd