Page 502 - Asterisk™: The Future of Telephony

[general]
Settings under the [general] section are used to customize the output of the logs (and
can safely be left blank, as the defaults serve most people very well). However, if you
love to customize such things, read on.

You can define exactly how you want your timestamps to look through the use of the
dateformat parameter:
dateformat=%F %T
The Linux manpage for strftime(3) lists all of the ways you can do this.

If you want to append your system’s hostname to the names of the logfiles, set append
hostname=yes. This can be useful if you have a lot of systems delivering logfiles to you.
If for some reason you do not want to log events from your queues, you can set
queue_log=no.
If generic events do not interest you, instruct Asterisk to omit them from the logfiles
by setting event_log=no.

[logfiles]
The [logfiles] section defines the types of information you wish to log. There are
multiple ranks for the various bits of information that will be logged, and it can be
desirable to separate log entries into different files. The general format for lines in the
[logfiles] section is filename => levels, where filename is the name of the file to save
the logged information to and levels are the types of information you wish to save.

Using console for the filename is a special exception that allows you to
control the type of information sent to the Asterisk console.

A sample [logfiles] section might look like this:
[logfiles]
console => notice,warning,error
messages => notice,warning,error
You can specify logging of the following types of information:
debug
Enabling debugging gives far more detailed output about what is happening in the
system. For example, with debugging enabled, you can see what DTMF tones the
users entered while accessing their voicemail boxes. Debugging information should
be logged only when you are actually debugging something, as it will create massive
logfiles very rapidly.

474 | Appendix D: Configuration Files