2 ; Logging Configuration
4 ; In this file, you configure logging to files or to
7 ; "logger reload" at the CLI will reload configuration
8 ; of the logging system.
11 ; Customize the display of debug message time stamps
12 ; this example is the ISO 8601 date format (yyyy-mm-dd HH:MM:SS)
13 ; see strftime(3) Linux manual for format specifiers
16 ; This appends the hostname to the name of the log files.
19 ; This determines whether or not we log queue events to a file
23 ; This determines whether or not we log generic events to a file
28 ; For each file, specify what to log.
30 ; For console logging, you set options at start of
31 ; Asterisk with -v for verbose and -d for debug
32 ; See 'asterisk -h' for more information.
34 ; Directory for log files is configures in asterisk.conf
39 ; Format is "filename" and then "levels" of debugging to be included:
47 ; Special filename "console" represents the system console
49 ; We highly recommend that you DO NOT turn on debug mode if you are simply
50 ; running a production system. Debug mode turns on a LOT of extra messages,
51 ; most of which you are unlikely to understand without an understanding of
52 ; the underlying code. Do NOT report debug messages as code issues, unless
53 ; you have a specific issue that you are attempting to debug. They are
54 ; messages for just that -- debugging -- and do not rise to the level of
55 ; something that merit your attention as an Asterisk administrator. Debug
56 ; messages are also very verbose and can and do fill up logfiles quickly;
57 ; this is another reason not to have debug mode on a production system unless
58 ; you are in the process of debugging a specific issue.
61 console => notice,warning,error
62 ;console => notice,warning,error,debug
63 messages => notice,warning,error
64 ;full => notice,warning,error,debug,verbose
66 ;syslog keyword : This special keyword logs to syslog facility
68 ;syslog.local0 => notice,warning,error