Reading FileMaker Server logs: Event, Access, Stats, and DAPI
IntermediateUnderstand the four main log files FileMaker Server produces, what each records, and how to use them for troubleshooting.
What you'll learn
- The purpose of the Event, Access, Stats, and DAPI logs
- How to read and filter logs in Admin Console's Log Viewer
- What to look for when troubleshooting common problems
FileMaker Server maintains four persistent log files. Each records a different category of activity. Knowing which log to check first saves significant time when diagnosing connection problems, performance issues, or script failures.
The four log files
Event.log records server-level activity: starts, stops, schedule results, opens/closes of databases, errors, and client disconnects. Access.log records every file open and close by a client, including the username and IP address. Stats.log records server resource usage at configurable intervals: connected clients, cache hit percentage, elapsed time per operation. DAPI.log records every Data API request: method, path, response code, and elapsed time.
Sign in to track your progress and pick up where you left off.
Sign in to FM Dojo