Edgewall Software

Changes between Version 23 and Version 24 of TracLogging


Ignore:
Timestamp:
Mar 6, 2022, 9:01:02 AM (4 months ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified
  • TracLogging

    v23 v24  
    1919== Log Levels
    2020
    21 The verbosity level of logged messages can be set using the [TracIni#logging-log_level-option "[logging] log_level"] option. The log level defines the minimum level of urgency required for a message to be logged, and those levels are:
     21The verbosity level of logged messages can be set using the [TracIni#logging-log_level-option "[logging] log_level"] option. The log level defines the minimum level of urgency required for a message to be logged:
    2222
    2323 '''CRITICAL''':: Log only the most critical (typically fatal) errors.
     
    2727 '''DEBUG''':: Trace messages, profiling, etc.
    2828
    29 Additionally, you can  enable logging of SQL statements at debug level. This is turned off by default, as it's very verbose. Set [TracIni#trac-debug_sql-option "[trac] debug_sql  = yes"] to activate.
     29Additionally, you can enable logging of SQL statements at debug level. This is turned off by default, as it's very verbose. Set [TracIni#trac-debug_sql-option "[trac] debug_sql  = yes"] to activate.
    3030
    3131== Log Format
     
    4343}}}
    4444
    45 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:
     45In 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` as that can generally be used to identify a project:
    4646{{{#!ini
    4747log_format = Trac[$(basename)s:$(module)s] $(levelname)s: $(message)s