On 4/25/07, Steve Huston <[EMAIL PROTECTED]> wrote:
On 4/25/07 12:39 PM, Chet Luther wrote:
> Zenoss will definitely support this case. It's probably the most
> common usage of the event mapping system. All you need to do is create
> separate event classes for these events.
That's a lot of classes when you're looking at over 650 traps. Is there
some reason the /HW/Power class is insufficient for this task?
> I'd do it something like
> this:
Here's what I have:
/HW/Power/upsTurnedOff:
zEventAction = status (Default for /)
zEventClearClasses = upsTurnedOn
zEventSeverity = Critical
/HW/Power/upsTurnedOn
zEventAction = history
zEventClearClasses = [blank, default for /]
zEventSeverity = Clear
/HW/Power/upsBatteryNeedsReplacement
zEventAction = status (Default)
zEventClearClasses = upsBatteryReplaced
zEventSeverity = Critical
The problem is that when the upsTurnedOn trap comes in,
upsBateryNeedsReplacement gets sent to the history.
This is because the zEventClearClasses clears classes, not class keys.
--
Chet Luther
[EMAIL PROTECTED]
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
