First of all I don’t have a problem with CheckMK, but in the way that ‘on the job’ it can create unwanted notification. How would to solve this? Do you have tips or idea’s?
Current we are using CheckMK Enterprise 1.6.0p13 with the following rule (as example)
But when people are patching, create database dump or something else, a filesystem can fill up from 0% to 50% in short time. In this example /var/cache will be fill and cleaned after work is done. Currently we get the following notification:
Service: Filesystem /var/cache, Status: WARNING, Status information: WARN - 55.13% used (1.1 of 1.99 GB), (warn/crit at 84.14%/92.07%), trend: +753.89 MB / 24 hours - only 29 hours until disk fullWARN
Idea’s that I had:
- Ask CheckMK for a minimum parameter. So that notification only be create when filesystem is higher then 60%.
- Exclude filesystem from the main rule and create rule without Trend calculation
- Do you have options/idea’s???