Another nice intro article, however a couple i would like to add a couple of quick points your readers may be interested in…

1) Since writing to the console must occur at it’s configured speed (default 9600 bps) this can cause increased in CPU usage(if it suddenly has to write 000s of messages* at that speed and in each case wait until it has finished witting the last this can cause problems. It is a while since I have seen this on live equipment and am unsure if this is due to better scheduling within IOS. However I would still consider it good practice to disable console logging except for a specific purposes.

2) While not “better” than the methods above I thought I would mention the way I usually check if the (telnet/shh) session logged in has logging enabled, as an alternative:
LabR1SW3#sh term | inc Cap
Capabilities: Receives Logging Output

For new Cisco users it probably worth pointing out the other useful items in the sh term output as part of your Console Mastery series.

*e.g. if debugging is enabled