Get a free year on Tuts+ this month when you purchase a Siteground hosting plan from $3.95/mo
A well written program on the Mac will log messages to the system log. Anyone can view the log using Mac’s Console program, but very few people know about it. In this tutorial, I'll show you how to use the Console and the different things you can do with it.
To open Console, go to the Utilities directory under Applications in the Dock.
Or, open Spotlight and launch it from there.
If you have Alfred, you can type console in the Alfred prompt.
If you have LaunchBar, you can open it with Console as well.
Whichever way you launch Console, the program will show a lot of information on the main window. What you see is every message that every program you are running sends to the System Log.
The System Log is a unified way to store information about program states on the Mac. Typically, each line shows the time recorded and the message given from the program.
Button Bar Functions
The first button in the button bar is Show Log List. This will open a side-panel to the left and show all the files that it reads log information from to generate the list.
The All Messages area has entries from each of these files. If you select a single file, it will display information from that file.
The Clear Display button clears everything in the main window area. This comes in handy to see new messages.
The Reload button will reload the information from all the log files. Therefore, if you Clear Display or Ignore Sender, the information hidden is re-written to the list.
The Ignore Sender button gives a way to narrow down the information. Select an entry, click the Ignore Sender button, and every entry from that sender is not shown. You can reverse it by doing a Reload.
In my Console window, I have many entries from com.apple.time that I do not need to see. By selecting one of them…
and then pressing Ignore Sender, all lines from the com.apple.time sender get removed. To undo this, press Reload and they will be back.
With the Insert Marker, you can put a time stamped entry at that location. The first time you do one, I have found it necessary to do it from the View menu. After that, you can do it from the button just fine.
With the marker in place, you can go back to work. When you check it again, you can easily see the marker and any newer entries.
The Inspector button turns on and off an entry inspector. When you select an entry and press Inspector, more detailed information about the selected entry gets shown in an easy to read format. You can move this windows over to the side and select different entries. The Inspector will show the information for that entry.
The last item is the Filter. This looks like a search box, but is rather a way to remove all entries except for the ones that match the string in the Filter box. Therefore, if you know a piece of text you need to find in the logs, type it in the Filter box and every entry with that text will show up. Looking for all FIXME text strings really gives a large number of entries. Looks like a bug!
Those FIXME entries show that I have a definite bug that I have to fix. The message mostly comes from the SystemUIServer process. This process takes care of external hardware attached by my computer. The string it shows is BBFFFLO?
Since I have a Buffalo USB hard drive, that’s probably the problem.
After I unmounted and removed the Buffalo USB drive, I placed a marker after the last entry of that type. By inspecting the previous log entries, I can see that I am getting a FIXME entry 12 times a second! Thirty minutes latter and I have no messages. That was definitely the problem.
As soon as I plug the Buffalo Drive back up, I instantly start having those messages again. I also notice that the diskarbitrationd process has the same issue. It must be the volume name of the disk isn’t written using UTF–8 characters.
By searching the Internet, I found out how to change the volume name. No more problems. Now, my log files will be much smaller! Not only that, but access times to the external hard drive improved greatly.
That bad volume name shows the value of the Console program. By inspecting the Console every now and then, you can get a feel for the health of your system, spot suspicious errors, and keep your system running the best it can. Searching the Internet for the processes shown in the Console will help you narrow down the issue until you can fix it yourself.