logging

In addition to startup logs, user activity and server events can be logged to files. Logs are aggregated daily and kept forever unless configured otherwise.

# example
logging: 
  # Access log (user activity over SSH)
  access:
    # Directory where logs will be kept
    location: D:\buru\logs\access
    
    # keep files forever
    maxFileCount: 0
    
  # Server log (for debugging purposes)
  server:
    location: D:\buru\logs\server
    # Minimum log level to write. Set to warning by default.
    # Supported values are: verbose, debug, information, warning, error and fatal. 
    minLevel: warning
    
    # keep at most 31 files (~1 month)
    maxFileCount: 31

logging.access

object

Log file configuration for machine-parseable user activity logs.

logging.access.location

string

Directory where access logs will be kept.

logging: 
    # ...
    access:
        # ...
        location: 'D:\buru\logs'

logging.access.maxFileCount

number = 0

Maximum number of log files to keep (oldest files exceeding the limit will be deleted). Set to 0 to keep all files.

logging.server

Log

Log file configuration for SSH server event logs.

logging.server.location

string

Directory where server event logs will be kept.

logging:
    # ...
    server:
        # ...
        location: 'D:\buru\logs'

logging.server.maxFileCount

number = 0

Maximum number of log files to keep (oldest files exceeding the limit will be deleted). Set to 0 to keep all files.

logging.server.minLevel

string: "verbose" | "debug" | "information" | "warning" | "error" | "fatal" = "warning"

Minimum log level to write.

logging:
  # ...
  server: 
    # ...
    minLevel: debug

logging.useCustomConfig

boolean = false

Experienced users can enable custom logging using useCustomConfig option. You can find more details on dedicated documentation page.

logging:
  useCustomConfig: true