First, if you enable the highest level of logging, you may get a performance hit. Generally, enabling the Debug level is only for troubleshooting. There are 8 levels of logging:
0 - Emergencies - system is unusable
1 - Alerts - Immediate action needed
2 - Critical - Critical conditions
3 - Errors - Error conditions
4 - Warnings - Warning conditions
5 - Notifications - Informational messages
6 - Informational - Normal but significant conditions
7 - Debugging - debug messages
Generally, if you want to be able to actually READ the logging files, setting to level 5 - Notifications would be enough. To capture the most information, set it to 6 - Informational.
#logging buffered info (if you want to see the logs on the PIX, "sho logg")
#logging trap info (or "notif" for less clutter)
I generally use the "informational" level on the trap (syslog) setting, and "notification" on the buffered logging.
#logging timestamp (add timestamps to logging)
You can enable the other logging options, but this could cause issues. (console logging will log to your console session, making it hard to see any commands entered or other information, Monitor logging will log to your remote access session (telnet, ssh))
NP... It is usually a good idea to keep timestamps on if you syslog multiple devices, so you can correlate log entries if any issues happen. (and, of course, Time Servers and NTP on all devices to keep them syncronized.)
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...