Edgewall Software

Changes between Version 10 and Version 11 of TracLogging


Ignore:
Timestamp:
Jan 16, 2007, 4:10:45 PM (17 years ago)
Author:
maz <mzizka@…>
Comment:

Added log format info (#2844)

Legend:

Unmodified
Added
Removed
Modified
  • TracLogging

    v10 v11  
    2626 '''DEBUG''':: Trace messages, profiling, etc.
    2727
     28== Log Format ==
     29
     30Starting 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 [wiki:TracIni#logging-section trac.ini]. The format is a string which can contain any of the [http://docs.python.org/lib/node422.html Python logging Formatter variables]. Additonally, the following Trac-specific variables can be used:
     31 '''$(basename)s''':: The last path component of the current environment.
     32 '''$(path)s''':: The absolute path for the current environment.
     33 '''$(project)s''':: The originating project's name.
     34
     35Note that variables are identified using a dollar sign (`$(...)s`) instead of percent sign (`%(...)s`).
     36
     37The default format is:
     38{{{
     39log_format = Trac[$(module)s] $(levelname)s: $(message)s
     40}}}
     41
     42In 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:
     43{{{
     44log_format = Trac[$(basename)s:$(module)s] $(levelname)s: $(message)s
     45}}}
     46
    2847----
    2948See also: TracIni, TracGuide, TracEnvironment