FileMaker Server Log Management

Intermediate

Understand the FileMaker Server log files, what each contains, and how to use them for troubleshooting and security monitoring.

What you'll learn

  • The four main FileMaker Server log files and their locations
  • What each log records and how to read it
  • Using logs for security monitoring and incident response
  • Log rotation and retention management

FileMaker Server maintains several log files that record connection activity, server events, and errors. These logs are your primary diagnostic resource for troubleshooting problems and monitoring security. Knowing which log contains what information saves significant time during incidents.

1/4
1

The four main log files

**access.log**: Records every client connection -- account name, client IP, file accessed, connection duration, bytes transferred. Primary resource for security monitoring and usage analysis. **event.log**: Records server-level events -- file open/close, schedule execution, admin actions, errors. Best for operational troubleshooting. **stderr.log / stdout.log**: Low-level process output. Useful for deep debugging. Rarely needed for day-to-day work. **ClientStats.log**: Per-client statistics. Useful for capacity planning.

TEXT
// Log file locations:
// macOS:
// /Library/Logs/FileMakerServer/FileMakerServer_Event.log
// /Library/Logs/FileMakerServer/FileMakerServer_Access.log

// Windows:
// C:\Program Files\FileMaker\FileMaker Server\Logs\FileMakerServer_Event.log
// C:\Program Files\FileMaker\FileMaker Server\Logs\FileMakerServer_Access.log
FileMaker Server Backup StrategyBack to FileMaker Server

Sign in to track your progress and pick up where you left off.

Sign in to FM Dojo