comparison: asterisk/logger.conf
asterisk/logger.conf
- changeset 310
- 73d852a30c9a
equal
deleted
inserted
replaced
| 0:846a12277847 | -1:000000000000 |
|---|---|
| 1 ; | |
| 2 ; Logging Configuration | |
| 3 ; | |
| 4 ; In this file, you configure logging to files or to | |
| 5 ; the syslog system. | |
| 6 ; | |
| 7 ; "logger reload" at the CLI will reload configuration | |
| 8 ; of the logging system. | |
| 9 | |
| 10 ;[general] | |
| 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 | |
| 14 ;dateformat=%F %T | |
| 15 ; | |
| 16 ; This appends the hostname to the name of the log files. | |
| 17 ;appendhostname = yes | |
| 18 ; | |
| 19 ; This determines whether or not we log queue events to a file | |
| 20 ; (defaults to yes). | |
| 21 ;queue_log = no | |
| 22 ; | |
| 23 ; This determines whether or not we log generic events to a file | |
| 24 ; (defaults to yes). | |
| 25 ;event_log = no | |
| 26 ; | |
| 27 ; | |
| 28 ; For each file, specify what to log. | |
| 29 ; | |
| 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. | |
| 33 ; | |
| 34 ; Directory for log files is configures in asterisk.conf | |
| 35 ; option astlogdir | |
| 36 ; | |
| 37 ;[logfiles] | |
| 38 ; | |
| 39 ; Format is "filename" and then "levels" of debugging to be included: | |
| 40 ; debug | |
| 41 ; notice | |
| 42 ; warning | |
| 43 ; error | |
| 44 ; verbose | |
| 45 ; dtmf | |
| 46 ; | |
| 47 ; Special filename "console" represents the system console | |
| 48 ; | |
| 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. | |
| 59 ; | |
| 60 ;debug => debug | |
| 61 ;console => notice,warning,error | |
| 62 ;console => notice,warning,error,debug | |
| 63 ;messages => notice,warning,error | |
| 64 ;full => notice,warning,error,debug,verbose | |
| 65 | |
| 66 ;syslog keyword : This special keyword logs to syslog facility | |
| 67 ; | |
| 68 ;syslog.local0 => notice,warning,error | |
| 69 ; |
