On 4/26/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi:
I'm pretty new to zenoss. I had no problem installing it and
configuring it to monitor our network of 45 or so Unix and Windows
servers. It appears to be really slick.
I've noticed that some events become more severe as time elapses.
E.g., some of our Windows cpuPercentProcessorTime events (which are
mapped to /Perf/CPU) have severity 3, but if the condition isn't
cleared, subsequent events have severity 4. Is this severity
increment something that's done by zenoss? Or by the SNMP agent? If
zenoss, where's it done, and can the behaviour be configured? If not,
could it be done by zenoss and, if so, where?
We would like to implement similar behaviour for /Status/Ping events
on our Windows servers (which are constantly being rebooted at varous
times of the day). That is, when zenoss notices that a Windows box is
unresponsive, we'd like this to be reported with severity 3 and only
be upped to a severity 5 when the machine is down for five minutes or
more. Where would we make this change?
Cliff,
This escalation is being done by Zenoss, and is easy to setup.
However, it is only available on performance thresholds (such as
cpuPercentProcessorTime.) To get some of this functionality for ping
events you'd want to look into setting the "delay" on your alert rule
to 300 seconds. This way the ping failures would still impact the
device's availablity reports, but you wouldn't get emailed/paged about
them.
Just FYI, the escalation behavior for performance thresholds can be
configured by going to a device's PerfConf tab then to the data source
you're interested in. On the data source's tab you would set the
severity to the starting severity, then the escalate count to how many
of these events have to happen before the severity is bumper up one
value.
Hope this helps.
--
Chet Luther
[EMAIL PROTECTED]
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
