Both folke and laird at pando.com support exactly what I am saying. Is this typical Zenoss behavior? I would think there would have to be a way to minimize the lower level alerts and concentrate on bigger events. It appears that this was thought about in development with zWinEventlogMinSeverity, but the system still sends lower priority alerts if I set it for 1. For instance, I won't be too concerned if one of my machines can't contact a domain controller to update time but I would be concerned if SMTP locked up. I hope someone has a suggestion for me. This is the only thing holding me back from a full implementation. Thanks in advance for the assistance.
Try restarting zeneventlog after changing the zWinEventlogMinSeverity property. Setting it to 1 should definitely result in only "Error" events being recorded. You can find the table of what the numbers mean at http://msdn2.microsoft.com/en-us/library/Aa394226.aspx under EventType.
Aside from that, the event mapping system was designed to allow modification of incoming events. If an event comes in that isn't as severe as Zenoss claims it to be, you can create a rule to downgrade the severity to something more appropriate.
_______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
