Thank you j_a_catlin and kstone for your replies. So, agreed, using a syslog filter should be able to assist in syslog management. The logical follow-up question becomes, "How to build a list/definition of actionable vs trivial syslog messages. I'm sure if I looked at some messages, I could determine some were actionable,and some trivial. However, there must be thousands of syslog messages, so the likelihood of me defining each one seem remote.
Is there a list of actionable (or non-actionable) syslog messages you use? I am not intending this to be a "Here, let me Google that for you." type of question. I did a google, and immediately found a resource from Cisco which has an appendix of actionably syslog messages. Or, do you just filter for severity level? What process did you go through to build your actionable syslog filter?
Many Thanks, Eric