|Version 2 (modified by trac, 5 years ago)|
Table of Contents
Trac supports logging of system messages using the standard logging module that comes with Python.
Logging is configured in the [logging] section in trac.ini.
Supported Logging Methods
The log method is set using the log_type option in trac.ini, which takes any of the following values:
- Suppress all log messages.
- Log messages to a file, specified with the log_file option in trac.ini.
- Output all log entries to console (tracd only).
- (UNIX) Send all log messages to the local syslogd via named pipe /dev/log. By default, syslog will write them to the file /var/log/messages.
- (Windows) Use the system's NT Event Log for Trac logging.
The verbosity level of logged messages can be set using the log_level option in trac.ini. The log level defines the minimum level of urgency required for a message to be logged, and those levels are:
- Log only the most critical (typically fatal) errors.
- Log failures, bugs and errors.
- Log warnings, non-interrupting events.
- Diagnostic information, log information about all processing.
- Trace messages, profiling, etc.
Starting with Trac 0.10.4 (see #2844), it is possible to set the output format for log entries. This can be done through the log_format option in trac.ini. The format is a string which can contain any of the Python logging Formatter variables. Additonally, the following Trac-specific variables can be used:
- The last path component of the current environment.
- The absolute path for the current environment.
- The originating project's name.
Note that variables are identified using a dollar sign ($(...)s) instead of percent sign (%(...)s).
The default format is:
log_format = Trac[$(module)s] $(levelname)s: $(message)s
In a multi-project environment where all logs are sent to the same place (e.g. syslog), it makes sense to add the project name. In this example we use basename since that can generally be used to identify a project:
log_format = Trac[$(basename)s:$(module)s] $(levelname)s: $(message)s