Package: munin Version: 1.2.6-6 Severity: normal Hi, the check for values above the warning or critical threshold levels seems to have changed from 1.2.5. When e.g. the »df« plugin detects a new mount point (say a plugged in USB stick) it triggers the »contact.*.command«'s with:
example.com :: foo.example.com:: Disk usage (in percent) UNKNOWNs: /media/usb0 is unknown just to report 5 minutes later that the free disk space for that mount points is OK. The same happens when completely enabling new plugins - the state for all values is UNKNOWN, then OK. If munin doesn't find any values if shouldn't trigger with UNKNOWN but instead wait until it has a defined status - otherwise it generates lots of unnecessary UNKNOWN->OK flip flop mails, SMS, nagios events or whatever the contact.*.commands are wired to. -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]