It seems that in 2.1.1 thresholds, considering all previous posts,
are quite
borken. I did manage to find one more "bug".
In MinMaxThreshold.py, line 195:
if self.escalateCount and self.count >= self.escalateCount:
severity = max(severity + 1, 5)
summary = '%s %s threshold of %s %s: current value %.2f'
% (
So what is here written is that when severity is incremented, get
larger value
between new severity and 5! So, when your event rise, it will end up
on level
5, always!
I'm guessing that instead "max" here should be "min". :-)
Thank you for bringing this up! The logic was definitely backwards.
I've applied the fix and tagged the fix for inclusion into the 2.1
stable branch which will get it included with 2.1.2.
Ticket: http://dev.zenoss.org/trac/ticket/2394
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
