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.
12 ; Customize the display of debug message time stamps
13 ; this example is the ISO 8601 date format (yyyy-mm-dd HH:MM:SS)
15 ; see strftime(3) Linux manual for format specifiers. Note that there is also
16 ; a fractional second parameter which may be used in this field. Use %1q
17 ; for tenths, %2q for hundredths, etc.
19 ;dateformat=%F %T ; ISO 8601 date format
20 ;dateformat=%F %T.%3q ; with milliseconds
23 ; This makes Asterisk write callids to log messages
27 ; This appends the hostname to the name of the log files.
30 ; This determines whether or not we log queue events to a file
34 ; Determines whether the queue_log always goes to a file, even
35 ; when a realtime backend is present (defaults to no).
36 ;queue_log_to_file = yes
38 ; Set the queue_log filename
39 ; (defaults to queue_log)
40 ;queue_log_name = queue_log
42 ; When using realtime for the queue log, use GMT for the timestamp
43 ; instead of localtime. The default of this option is 'no'.
44 ;queue_log_realtime_use_gmt = yes
46 ; Log rotation strategy:
47 ; none: Do not perform any logrotation at all. You should make
48 ; very sure to set up some external logrotate mechanism
49 ; as the asterisk logs can get very large, very quickly.
50 ; sequential: Rename archived logs in order, such that the newest
51 ; has the highest sequence number [default]. When
52 ; exec_after_rotate is set, ${filename} will specify
53 ; the new archived logfile.
54 ; rotate: Rotate all the old files, such that the oldest has the
55 ; highest sequence number [this is the expected behavior
56 ; for Unix administrators]. When exec_after_rotate is
57 ; set, ${filename} will specify the original root filename.
58 ; timestamp: Rename the logfiles using a timestamp instead of a
59 ; sequence number when "logger rotate" is executed.
60 ; When exec_after_rotate is set, ${filename} will
61 ; specify the new archived logfile.
62 ;rotatestrategy = rotate
64 ; Run a system command after rotating the files. This is mainly
65 ; useful for rotatestrategy=rotate. The example allows the last
66 ; two archive files to remain uncompressed, but after that point,
67 ; they are compressed on disk.
69 ; exec_after_rotate=gzip -9 ${filename}.2
72 ; For each file, specify what to log.
74 ; For console logging, you set options at start of
75 ; Asterisk with -v for verbose and -d for debug
76 ; See 'asterisk -h' for more information.
78 ; Directory for log files is configures in asterisk.conf
83 ; Format is "filename" and then "levels" of debugging to be included:
93 ; Special filename "console" represents the system console
95 ; Filenames can either be relative to the standard Asterisk log directory
96 ; (see 'astlogdir' in asterisk.conf), or absolute paths that begin with
99 ; Special level name "*" means all levels, even dynamic levels registered
100 ; by modules after the logger has been initialized (this means that loading
101 ; and unloading modules that create/remove dynamic logger levels will result
102 ; in these levels being included on filenames that have a level name of "*",
103 ; without any need to perform a 'logger reload' or similar operation). Note
104 ; that there is no value in specifying both "*" and specific level names for
105 ; a filename; the "*" level means all levels, and the remaining level names
108 ; Verbose takes an additional argument, in the form of an integer level.
109 ; Messages with higher levels will be ignored. If verbose is specified at
110 ; all, it will default to 3.
112 ; We highly recommend that you DO NOT turn on debug mode if you are simply
113 ; running a production system. Debug mode turns on a LOT of extra messages,
114 ; most of which you are unlikely to understand without an understanding of
115 ; the underlying code. Do NOT report debug messages as code issues, unless
116 ; you have a specific issue that you are attempting to debug. They are
117 ; messages for just that -- debugging -- and do not rise to the level of
118 ; something that merit your attention as an Asterisk administrator. Debug
119 ; messages are also very verbose and can and do fill up logfiles quickly;
120 ; this is another reason not to have debug mode on a production system unless
121 ; you are in the process of debugging a specific issue.
124 ;security => security
125 console => notice,warning,error
126 ;console => notice,warning,error,debug
127 messages => notice,warning,error
128 ;full => notice,warning,error,debug,verbose,dtmf,fax
130 ;syslog keyword : This special keyword logs to syslog facility
132 ;syslog.local0 => notice,warning,error