Stewart

A big part of server monitoring is to know when error events are generated (and respond to them). A better solution would be to prevent duplicate events from appearing in the notification box (preventing it from filling up quickly), and having the ability to exclude any innocuous errors from reappearing (i.e. blacklist). How am I supposed to know in advance that there is a "SideBySide" failure that requires my attention (and add the appropriate keyword)? Or that the W32Time service isn't able to contact a valid time source? What good is the ability to monitor the event log if I'm not notified of these errors? Even a simple notification that "There are 32 new Error events in the event log" would be helpful.