Configure FileBrowser’s logging system.

For troubleshooting and enabling debug logs, see Debug Logging.

Default Logging

Without configuration, logs to stdout with INFO, WARNING, ERROR, and API levels with colors enabled.

Configuration

Enable Debug Logging

Debug logging allows for more granular info-level logs which can be very helpful if you see issues.

server:
  logging:
    - output: stdout
      levels: "info|warning|error|debug"

Log to File

You can log to a file instead of stdoiut by choosing a filepath as “output”.

server:
  logging:
    - output: "/var/log/filebrowser.log"
      levels: "info|warning|error"
      noColors: true

Multiple Outputs 

server:
  logging:
    # Terminal
    - output: stdout
      levels: "info|warning|error"
      apiLevels: disabled
    # API logs
    - output: "api-events.log"
      levels: disabled
      noColors: true
    # Errors
    - output: "errors.log"
      levels: "error|warning"
      apiLevels: disabled
      noColors: true

Json format

FileBrowser Quantum supports json formatted logging for improved indexed logging.

server:
  logging:
    - levels: "info|warning|error"
      json: true

Configuration Options

output

  • stdout or omit: Log to console
  • "path/to/file.log": Log to file

levels

Specify which levels to log: "info|warning|error|debug" or disabled

apiLevels

Same format as levels, but for API events

noColors

Disable colored output (recommended for files)

Log Levels

  • info - General information
  • warning - Warning messages
  • error - Error messages
  • debug - Detailed debugging with line numbers
  • api - API request/response logs

Next Steps