The FileMaker Server Configuration has a Log-In Tab and new to FileMaker 10 there's a also a Log Viewer. This is where we'll be for this movie. On this Log-In Tab we'll see that FileMaker Server automatically and by default logs events. That is not something that you can disable. Additionally, you can choose to also log access and statistics. All of these logs end up in FileMaker Server's Log Folder, right here in FileMaker's folder structure under Logs. This is where all the Log Files get created. And on Windows, we'll find the same folder right here. New in FileMaker Server 10 is that client actions related to hosted databases are logged in a separate access file. The log gets generated and or updated as long as this particular setting is turned On. And as you've seen, it's turned Off by default. In previous versions of FileMaker Server, the client actions were logged in the Event Log and you could not turn that off. For the statistics specifically, you can set how often FileMaker Server will collect performance data and that's in a range from once every second to every five minutes. And for both logs you can specify how big that log file can get. Once the log file reaches that file size limit, a new log file will be created. Back to statistics; what statistics are included in the log? Well, they are exactly what you would see on the statistics information pane. And this is the most relevant performance data for FileMaker Server. You can see how many clients are connected and what type of clients they are. You can see how many files are being hosted, what kind of network traffic is being generated, what kind of disk activity is going on, how much of the cache is unsaved and how much of the client's requests are handled from the database cache. You can also some interesting information about how long each call to FileMaker Server takes. These statistics and how they relate to optimum performance are handled in the monitoring movies later on in this tutorial. The log file itself is basically a tab within a text file. If you double click on it in OS X, it'll open up in the console app. The nice thing about the console app is that it lets you look at the logs while they are being updated live. On Windows, you can open up those log files in Notepad or Word, but they will not be updated automatically as events happen. Specifically for the access log file, you can open it up in say Excel and then use it to make some calculations or statistics about it. The larger you set the size, the more performance data you capture. Enabling the logging obviously has a small performance effect but that should be so small as to be unnoticeable. When the log file reaches the size limit you have set, it'll start a new file and save the old one. To avoid filling up the hard disk over time, make sure to archive the old files from time to time. You will also find some other log files in FileMaker's Admin Folder. And it might be a good idea to clean these out from time to time as well.