On Jan 19, 2009, at 2:35 PM, nxumdon wrote: > Just as an update, someone I was talking to mentioned that this > issue might be caused by the fact that I run Zenoss as a Linux VM. > I can't see how this would cause this alerting issue, but this > person swears that Zenoss was showing all sorts of problems while in > a VM, and they were all fixed by moving the box to real metal. > > Can anyone comment on this statement...could the fact that I'm > running this in a VM be causing this alerting problem? > > Really, what I need to know is if Zenoss does have some function for > suppression of msgs that fire quickly. If it does not, then the VM > idea might have some weight...but if Zenoss IS holding the msgs on > purpose, then it is just something I need to somehow tune.
While Zenoss doesn't have suppression for events that occur and clear very quickly, these kinds of events do go unnoticed by the alerting rules quite often. The reason is that the zenactions daemon only matches the active events against your configured alerting rules once per minute. If an event isn't in the active (status) table at this time, it won't be alerted on. Running in a VM should have no affect on this at all unless the VM is so slow and overburdened that it causes zenactions to run even less than once per minute. _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
