[zenoss-users] Re: false alarms

[James Pulver]

It looks like that might be talking about the ping monitor? If you go to 
Monitors under Management on the left, and Status Monitor, click 
localhost, you'll see you can go to edit and change the Ping Timeout.

But I don't see anything analogous for SNMP - you could change the cycle 
time, but I think they recommended against that at some point in the 
forums... But that would help if the Zenoss Server cannot get around to 
all SNMP checks in 5 minutes, you could make it 6 or 10 or whatever... 
But then you'd have a longer time before a change was noticed also I 
would think (unless it generates a trap).

Specifically, for reasons that are unknown, I'm seeing this with my 
Desktop PC with Informant (a testing system for Zenoss to monitor), if 
my PC is running something that is intensive like a VM, it'll often 
cause an SNMP is down alert - but if my PC finishes, then the alert 
clears. I guess my machine's SNMP might be down, but something that 
clears with the next cycle should be configurable - or somehow make it 
be 2 or 3 cycles to generate an alert.

However, I do think you might be able to do something with this in the 
Alert creation area, set count > 3 or something?
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University



raphael wrote:
> Is the status monitor ping related to "snmp down"?
> 
> Will this fix the problem:
> 
> " Simply adjust the status monitor's configuration to allow for more latency. If they don't come back at all you may need to raise the number of tries. "
> 
> 
> 
> 
> -------------------- m2f --------------------
> 
> Read this topic online here:
> http://community.zenoss.com/forums/viewtopic.php?p=15872#15872
> 
> -------------------- m2f --------------------
> 
> 
> 
> _______________________________________________
> zenoss-users mailing list
> zenoss-users at zenoss.org
> http://lists.zenoss.org/mailman/listinfo/zenoss-users