Actually I think you are trying to do two different things with your switch,
Monitor and log.
To monitor a switch you measure the different variables that you want to know something about.
To log (via syslog) you only get a syslog message telling you that X have happened.
To monitor you can use SNMP and both send traps or poll the device.
This is very good for fx checking how much data is transfered over an interface and get graphs over time of that information
or how much CPU is working, or memory, or temperature and such information.
basically things you want to have graphs of over time.
Logging is a different matter alltogeather.
logging is very good for things like checking if an access-list is hit, if there is an alarm going of for temperature or if the switch restarts, or if someone changes the configuration and such things.
In general things that does not happen that often and you do not need to get graphs over time for it.
To monitor I use SNMP to a monitor software that will show me the results in graphs and numbers.
if there is a problem the software will set of an alarm and send me a SMS and/or e-mail that something is not right.
To log I use a Syslog server that will let me log everything that I want and lets me filter the logs and show me what I want to see.
My general rule is to log everything and then filter out what you need for the moment.
if there is need for more logs afterwards then it is there.
Good luck
HTH
