michael@202: ;
michael@202: ; Logging Configuration
michael@202: ;
michael@202: ; In this file, you configure logging to files or to
michael@202: ; the syslog system.
michael@202: ;
michael@202: ; "logger reload" at the CLI will reload configuration
michael@202: ; of the logging system.
michael@202: 
michael@202: ;[general]
michael@202: ; Customize the display of debug message time stamps
michael@202: ; this example is the ISO 8601 date format (yyyy-mm-dd HH:MM:SS)
michael@202: ; see strftime(3) Linux manual for format specifiers
michael@202: ;dateformat=%F %T
michael@202: ;
michael@202: ; This appends the hostname to the name of the log files.
michael@202: ;appendhostname = yes
michael@202: ;
michael@202: ; This determines whether or not we log queue events to a file
michael@202: ; (defaults to yes).
michael@202: ;queue_log = no
michael@202: ;
michael@202: ; This determines whether or not we log generic events to a file
michael@202: ; (defaults to yes).
michael@202: ;event_log = no
michael@202: ;
michael@202: ;
michael@202: ; For each file, specify what to log.
michael@202: ;
michael@202: ; For console logging, you set options at start of
michael@202: ; Asterisk with -v for verbose and -d for debug
michael@202: ; See 'asterisk -h' for more information.
michael@202: ;
michael@202: ; Directory for log files is configures in asterisk.conf
michael@202: ; option astlogdir
michael@202: ;
michael@202: ;[logfiles]
michael@202: ;
michael@202: ; Format is "filename" and then "levels" of debugging to be included:
michael@202: ;    debug
michael@202: ;    notice
michael@202: ;    warning
michael@202: ;    error
michael@202: ;    verbose
michael@202: ;    dtmf
michael@202: ;
michael@202: ; Special filename "console" represents the system console
michael@202: ;
michael@202: ; We highly recommend that you DO NOT turn on debug mode if you are simply
michael@202: ; running a production system.  Debug mode turns on a LOT of extra messages,
michael@202: ; most of which you are unlikely to understand without an understanding of
michael@202: ; the underlying code.  Do NOT report debug messages as code issues, unless
michael@202: ; you have a specific issue that you are attempting to debug.  They are
michael@202: ; messages for just that -- debugging -- and do not rise to the level of
michael@202: ; something that merit your attention as an Asterisk administrator.  Debug
michael@202: ; messages are also very verbose and can and do fill up logfiles quickly;
michael@202: ; this is another reason not to have debug mode on a production system unless
michael@202: ; you are in the process of debugging a specific issue.
michael@202: ;
michael@202: ;debug => debug
michael@202: ;console => notice,warning,error
michael@202: ;console => notice,warning,error,debug
michael@202: ;messages => notice,warning,error
michael@202: ;full => notice,warning,error,debug,verbose
michael@202: 
michael@202: ;syslog keyword : This special keyword logs to syslog facility 
michael@202: ;
michael@202: ;syslog.local0 => notice,warning,error
michael@202: ;