Well, you can't suppress the threshold, but you can do an event
transform to lower the priority of the created event to info or 0? Which
might be right to history. This forum goes over that a bunch, but
basically what you'll want to do is something like
if evt.component == '<path>' and evt.severity != 0:
evt.severity = 0
in the /perf/filesystem event transforms. I don't think you can do this
at the device level, it's at the event class level(which means it would
affect any device that had <path> on it), but you *could* create an
event mapping that is first in the sequence before the default event
mapping for /perf/filesystem, and have it only match on the single
device and then map it to /Ignore. Other devices would "fall through" to
the normal one.
Or, as above
if evt.component == '<path>' and evt.device == '<device>' and
evt.severity != 0:
evt.severity = 0
Ware the wrap on the first line...
Maybe too many ways to do this, and I'm not actually aware of the
performance implications between the two methods(if any) - devs??
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
dwightmccann wrote:
I'm having a very similar issue: I have a filesystem on a single windows device
that is preallocated over 90% and I would like to suppress the 90% threshold
events for this one filesystem on this one device. I would expect this to be
trivially easy but it sure isn't obvious to me. I've done a dozen searches and
have found no one else with this question so I fear it is obvious to all but
me. [Laughing]
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=23613#23613
-------------------- 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
