Administrator’s Guide

38 FileMaker Server Administrator’s Guide
Mac OS: To configure log file properties, choose View menu >
Configure
, then click the Logging tab.
Controlling the collection of usage statistics
Use Collect and update usage statistics every n (mm:ss) to set the
statistics collection interval. FileMaker
Server writes this information
to a log file.
When you enable statistical logging for FileMaker Server, a log file is
created in the FileMaker Server/Data/Logs/ folder.
You can view these statistics by opening the Stats.log file in any
application that can read tab-delimited data (FileMaker
Pro, a
spreadsheet, or a text editor) or the Console application (Mac
OS).
You can also view real-time usage statistics in the Statistics view of
FileMaker Server Admin.
Note The Console application on the Mac OS allows you to view a
.log file while also displaying updates to that file.
For information on the types of statistics that are collected in the
statistics log, see
“Viewing usage statistics for FileMaker Server” on
page 50.
Managing log files
When Stats.log reaches its maximum size, FileMaker Server renames
it Stats-old.log and creates a new Stats.log.
Displaying statistics
In Windows, you can chart real-time statistics for various aspects of
FileMaker Server performance. See
“Monitoring server performance
(Windows)” on page 50.
Logging FileMaker Server events
Events that occur while FileMaker Server is running are logged and
timestamped. Typical events that are logged include FileMaker Server
starting and stopping, database files opening and closing, clients
logging in and out, scheduled tasks running, and changes to FileMaker
Server properties.
In Windows, events are logged in the Windows Application Log. For
more information, see
“Viewing activities in the Event Viewer
(Windows)” on page 51. In the Mac OS, events are logged in the tab-
delimited Event.log file that is created in the FileMaker Server/Data/
Logs/ folder. When this file reaches 40 MB, it is renamed Event-
old.log and a new Event.log file is created. For more information, see
“Viewing activities in the Event.log (Mac OS)” on page 51.
Configuring the Event Viewer (Windows)
You can configure the Event Viewer log files to overwrite event
information, because the default setting is to stop recording events
when the log files become full. If you have many databases open with
many users accessing them, and if you flush the cache often, the log
files could fill up quickly and the information in the log files could
quickly become out of date.
You can configure the Event Viewer log files by selecting the log file
in the Console Root and choosing
Action menu > Properties.
Operating
system
Statistics
log name View log in
Windows Stats.log 1 Performance Logs and Alerts (Windows 2000
Server)
1 System Monitor (Windows Server 2003)
Mac OS Stats.log 1 The Console application
1 Any application that can read tab-delimited data