What precisely is an Error?

What precisely is an unexpected event?

What issues are important for an administrator to investigate?

No doubt the answer to these questions is far from an immutable fact.

I have seen many cases where an "Unexpected" event is actually 100% normal for some customers in some situations.  These events can occur 100s, 1,000s, or 10,000s times a day.  The administrator knows what causes the warning and there is no action he needs to take and has no interest in seeing these warnings.  However, it is still necessary to actually read, view, and acknowledge EACH and every one over and over to ensure that other critical items he cares about are not missed.

It would be great if there could be an Administratively defined set of strings to prevent the uploading of errors/warnings that matched.  These would be parsed on the client before uploading to the primary.  This would lower overhead on the Primaries and Database, as the number of errors/warnings to be processed would be reduced.  The administrative overhead of acknowledging these warnings they already know they do not care about would be eliminated.  ZENworks Engineer resources could be lowered, since sometimes they are asked to recode the product to adjust error levels after a debate on what is or is not an "Error" vs "Warning" vs "Informational".  If the Administrator could filter these messages, it would lower the need to balance the needs of customers regarding what is an Error/Warning/Informational.