You could use an event transform to indicate you don't care about the
event. I turn down more general file system events with this:
if evt.component == '/mnt/filesystem' and evt.severity != 0:
evt.severity = 2
in the /perf/filesystem event class transform. This makes it info level
and so I don't get an alert, though I do get the event. Setting to 0 I
believe would move right to history, and there is a way that I don't
recall right off to drop the event here as well.
You certainly could use an event mapping to drop it I think.
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
reighnman wrote, On 2/4/2009 9:22 AM:
> I'm using the ESX Zenpack to monitor the file system of a couple ESX servers.
> One of the storage partitions is full (intended) as the machine is full on
> hosts which causes constant threshold events.
>
> When I check the partion > monitoring > off, threshold events persist (M is
> red). Push changes, clear heartbeats, events threshold persist. When I
> delete the file system from the list all together, threshold events persist.
>
> How can I work around this?
>
>
>
>
> -------------------- m2f --------------------
>
> Read this topic online here:
> http://forums.zenoss.com/viewtopic.php?p=30906#30906
>
> -------------------- 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
