It may be a transient error. You might want to try changing your alert
rule to only fire if
Count > 1
I've had to do this with a number of alerts, and it sort of makes sense
- you probably don't want an alert if Zenoss glitched, or your network
glitched, or the server was heavily loaded and timed out just then. But
if your service is down for several tries, then it's a problem.
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
makemorebeer wrote:
i've got about 29 servers loaded into zenoss, and i'm consistently getting
snmpdown on every other cycle from our PDC, and BDC's, and our exchange
server. i tried pushing back the polling cycle but it doesn't seem to have
done anything. just puts a larger space between the notifications. despite
this, everything seems to be working normally. Anyone else have the same
issue, or know why it might be doing this?
Thanks,
Beer
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=19353#19353
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
